[4490] in testers
named oddness
daemon@ATHENA.MIT.EDU (John Hawkinson)
Thu Jun 22 07:41:16 2000
Date: Thu, 22 Jun 2000 07:41:05 -0400 (EDT)
Message-Id: <200006221141.HAA06317@x15-cruise-basselope.mit.edu>
To: testers@mit.edu
From: John Hawkinson <jhawk@MIT.EDU>
[x15-cruise-basselope!jhawk] ~> machtype -L
8.4.4
I logged in this morning and ran netscape and tried to go to
www.nytimes.com, and was told "Netscape is unable to locate the
server"; sure enough, 'host' could not resolve it either.
Checking 'ndc dumpdb', I see:
$ORIGIN COM.
nytimes 172720 IN NS AUTH50.NS.UU.NET. ;Cr=answer
172720 IN NS GATEKEEPER.nytimes.com. ;Cr=answer
172720 IN NS UUCP-GW-1.PA.DEC.com. ;Cr=answer
172720 IN NS UUCP-GW-2.PA.DEC.com. ;Cr=answer
...
$ORIGIN nytimes.COM.
GATEKEEPER 172720 IN A 199.181.175.201 ;Cr=addtnl
;www 447 IN SOA A.ROOT-SERVERS.NET. hostmaster.internic.NET. (
; 2000062101 1800 900 604800 86400 );COM.;NXDOMAIN ;-$
;Cr=auth
But a.root-servers.net is not handing out such an NXDOMAIN for www.nytimes.com
anymore:
[x15-cruise-basselope!jhawk] ~> dig @a.root-servers.net www.nytimes.com a
; <<>> DiG 8.1 <<>> @a.root-servers.net www.nytimes.com a
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 5
;; QUERY SECTION:
;; www.nytimes.com, type = A, class = IN
;; AUTHORITY SECTION:
NYTIMES.COM. 2D IN NS AUTH50.NS.UU.NET.
NYTIMES.COM. 2D IN NS GATEKEEPER.NYTIMES.COM.
NYTIMES.COM. 2D IN NS UUCP-GW-1.PA.DEC.COM.
NYTIMES.COM. 2D IN NS UUCP-GW-2.PA.DEC.COM.
;; ADDITIONAL SECTION:
AUTH50.NS.UU.NET. 2D IN A 198.6.1.161
GATEKEEPER.NYTIMES.COM. 2D IN A 199.181.175.201
UUCP-GW-1.PA.DEC.COM. 2D IN A 16.1.0.18
UUCP-GW-1.PA.DEC.COM. 2D IN A 204.123.2.18
UUCP-GW-2.PA.DEC.COM. 2D IN A 16.1.0.19
;; Total query time: 20 msec
;; FROM: x15-cruise-basselope.mit.edu to SERVER: a.root-servers.net 198.41.0.4
;; WHEN: Thu Jun 22 07:37:27 2000
;; MSG SIZE sent: 33 rcvd: 234
I don't know how to account for this; a.root-servers.net's address
that dig talked to is the same as the one in named.root.
I suppose this is either a transient nameserver failure on a's part,
or a bizarre bug in named here. I report it so others might
be aware if we see a recurrance, but don't otherwise expect
anything to come of it...
--jhawk
