(cc to nanog in case anyone is wondering why they are having sporadic
problems reaching rs.internic.net...)
$ dig internic.net soa @noc.cerf.net
; <<>> DiG 2.2 <<>> internic.net soa @noc.cerf.net
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr aa rd ra; Ques: 1, Ans: 1, Auth: 5, Addit: 5
;; QUESTIONS:
;; internic.net, type = SOA, class = IN
;; ANSWERS:
internic.net. 86400 SOA ops.internic.net. markk.internic.net. (
98103001 ; serial
3600 ; refresh (1 hour)
3600 ; retry (1 hour)
432000 ; expire (5 days)
86400 ) ; minimum (1 day)
[...]
All the other servers have 98104001. This is a problem because (one of)
the changes made between those two revisions are to change rs.internic.net
from having:
rs.internic.net. 900 A 198.41.0.12
rs.internic.net. 900 A 198.41.0.13
rs.internic.net. 900 A 198.41.0.6
rs.internic.net. 900 A 198.41.0.7
rs.internic.net. 900 A 198.41.0.8
rs.internic.net. 900 A 198.41.0.9
to:
rs.internic.net. 900 A 198.41.0.6
Currently, rs.internic.net doesn't resolve to a functioning host when a
resolver asks noc.cerf.net for an answer, unless it happens to pick .6 out
of the list. It has been this way for at least a few hours and since the
refresh is 1h... people will see intermittent problems reaching
rs.internic.net
Of course, right now whois seems hosed anyway, but...:
$ whois internic.net
Registrant:
$
I've been having this problem intermittently for about 3 - 4 days now. I
would do a whois only to have it hit the HOD (Hang of Death(tm)) on me.
Basicly, out of 12 or so whois lookups, one would complete. I'd end up
with 13 or 14 open, hung connections to rs.internic.net.. Seems to be
having the same problems that hotmail was having 
(cc to nanog in case anyone is wondering why they are having sporadic
problems reaching rs.internic.net...)
$ dig internic.net soa @noc.cerf.net
; <<>> DiG 2.2 <<>> internic.net soa @noc.cerf.net
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr aa rd ra; Ques: 1, Ans: 1, Auth: 5, Addit: 5
;; QUESTIONS:
;; internic.net, type = SOA, class = IN
;; ANSWERS:
internic.net. 86400 SOA ops.internic.net. markk.internic.net. (
98103001 ; serial
3600 ; refresh (1 hour)
3600 ; retry (1 hour)
432000 ; expire (5 days)
86400 ) ; minimum (1 day)
[...]
All the other servers have 98104001. This is a problem because (one of)
the changes made between those two revisions are to change rs.internic.net
from having:
rs.internic.net. 900 A 198.41.0.12
rs.internic.net. 900 A 198.41.0.13
rs.internic.net. 900 A 198.41.0.6
rs.internic.net. 900 A 198.41.0.7
rs.internic.net. 900 A 198.41.0.8
rs.internic.net. 900 A 198.41.0.9
to:
rs.internic.net. 900 A 198.41.0.6
Currently, rs.internic.net doesn't resolve to a functioning host when a
resolver asks noc.cerf.net for an answer, unless it happens to pick .6 out
of the list. It has been this way for at least a few hours and since the
refresh is 1h... people will see intermittent problems reaching
rs.internic.net
Of course, right now whois seems hosed anyway, but...:
$ whois internic.net
Registrant:
$
_ __ _____ __ _________
______________ /_______ ___ ____ /______ John Gonzalez/Net.Engineer
__ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC!
_ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052
/_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com
[---------------------------------------------[system info]-----------]
3:35pm up 22 days, 19:04, 3 users, load average: 0.00, 0.03, 0.02