Mailing List Archive: h.root-servers.net broken

h.root-servers.net broken

Feb 13, 1997, 7:18 PM

Post #1 of 4 (386 views)

The DREN root nameserver has been broke for something more than an hour.
Would you please document some out-of-band method (telno, maybe) for contacting
the root nameserver ops folks? Gracias.

Cheers,
JH +1 408 731 3395

% dig ns yahoo.com @h.root-servers.net

; <<>> DiG 2.2 <<>> ns yahoo.com @h.root-servers.net
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10
;; flags: qr aa rd; Ques: 1, Ans: 0, Auth: 1, Addit: 0
;; QUESTIONS:
;; yahoo.com, type = NS, class = IN

;; AUTHORITY RECORDS:
. 86400 SOA A.ROOT-SERVERS.NET. hostmaster.INTERNIC.NET. (
1997021100 ; serial
10800 ; refresh (3 hours)
900 ; retry (15 mins)
604800 ; expire (7 days)
86400 ) ; minimum (1 day)

;; ...truncated
;; Total query time: 99 msec
;; FROM: borogove.yahoo.com to SERVER: h.root-servers.net 128.63.2.53
;; WHEN: Thu Feb 13 18:02:19 1997
;; MSG SIZE sent: 27 rcvd: 100

18:02:18.961232 borogove.yahoo.com.ms-sna-server > h.root-servers.net.domain: 10+ NS? yahoo.com. (27)
4500 0037 eddb 0000 4011 9a4c cdd8 a241
803f 0235 05c5 0035 0023 b9f3 000a 0100
0001 0000 0000 0000 0579 6168 6f6f 0363
6f6d 0000 0200 01
18:02:19.035840 h.root-servers.net.domain > borogove.yahoo.com.ms-sna-server: 10 NXDomain*- 0/1/0 (100)
4500 0080 e913 0000 3311 abcb 803f 0235
cdd8 a241 0035 05c5 006c d257 000a 8503
0001 0000 0001 0000 0579 6168 6f6f 0363
6f6d 0000 0200 0100 0006 0001 0001 5180
003e 0141 0c52 4f4f 542d 5345 5256 4552
5303 4e45 5400 0a68 6f73 746d 6173 7465
7208 494e 5445 524e 4943 c035 7708 1fac
0000 2a30 0000 0384 0009 3a80 0001 5180
18:02:22.707358 borogove.yahoo.com.lansource > i.root-servers.net.domain: 10+ NS? yahoo.com. (27)
4500 0037 ee03 0000 4011 c862 cdd8 a241
c024 9411 05cd 0035 0023 e829 000a 0100
0001 0000 0000 0000 0579 6168 6f6f 0363
6f6d 0000 0200 01
18:02:22.958964 i.root-servers.net.domain > borogove.yahoo.com.lansource: 10- 4/0/3 NS NS.YAHOO.CA. (161)
4500 00bd 76aa 0000 2f11 5036 c024 9411
cdd8 a241 0035 05cd 00a9 144f 000a 8100
0001 0004 0000 0003 0579 6168 6f6f 0363
6f6d 0000 0200 01c0 0c00 0200 0100 02a3
0000 0d02 4e53 0559 4148 4f4f 0243 4100
c00c 0002 0001 0002 a300 000e 0457 5757
3206 4555 524f 5045 c00c c00c 0002 0001
0002 a300 0005 024e 53c0 0cc0 0c00 0200
0100 02a3 0000 0603 4156 31c0 0cc0 4000
0100 0100 02a3 0000 04c3 e850 05c0 5a00
0100 0100 02a3 0000 04cd d892 5dc0 6b00
0100 0100 02a3 0000 04cc 7b02 55
- - - - - - - - - - - - - - - - -

Re: h.root-servers.net broken [ In reply to ]

jamesf at arl

Feb 13, 1997, 9:57 PM

Post #2 of 4 (385 views)

Permalink

All,

The problem on h.root-servers.net is fixed. Temporarily lost the COM
zone. Situation Normal: All Fixed Up. :-) Thanks for reporting the problem.
If you have any more problems, please report them to our operations staff
at (410)278-6829 or (410)278-6642. They'll contact me at home.

James Fielding
<jamesf@arl.mil>
- - - - - - - - - - - - - - - - -

Re: h.root-servers.net broken [ In reply to ]

pjnesser at martigny

Feb 13, 1997, 11:20 PM

Post #3 of 4 (385 views)

Permalink

Not knowing what actually went on with the name-servers that have gone
haywire today this is only speculation but I wanted to point it out since
it may be a possibility.

There have been a number of very dissatisfied people about the IAHC domain
name debate who have made public treats to enact cyber terrorism. One of
the items that they specifically have treatened is to try and kill all the
traditional root nameservers so that the public will be forced to use their
alternic nameservers.

I want to make it clear that I am not making any accusations, but just want
to raise the possibility so that those cleaing up won't inadverently loose
possible evidence in case this was a deliberate act.

---> Phil
- - - - - - - - - - - - - - - - -

Re: h.root-servers.net broken [ In reply to ]

kupiec at jvnc

Feb 14, 1997, 3:09 PM

Post #4 of 4 (383 views)

Permalink

In article <9702140044.aa12117@sparky.arl.mil> you write:
>All,
>
> The problem on h.root-servers.net is fixed. Temporarily lost the COM
>zone. Situation Normal: All Fixed Up. :-) Thanks for reporting the problem.
>If you have any more problems, please report them to our operations staff
>at (410)278-6829 or (410)278-6642. They'll contact me at home.
>
> James Fielding
> <jamesf@arl.mil>

Do you know during what time period that you lost .com? I first
noticed it a few minutes after noon EST and the problem seemed to be
corrected around midnight EST.

It would be nice to know during what time I can attribute yesterday's
problems to a root server failing, and not to my DNS servers failing.

--
Bob Kupiec GES / WNA
http://www.ges.com/~kupiec Princeton, NJ
- - - - - - - - - - - - - - - - -