[30432] in North American Network Operators' Group
Re: g.root-servers.net returns NXDOMAIN for com.
daemon@ATHENA.MIT.EDU (Mark Milhollan)
Fri Aug 4 11:09:23 2000
To: nanog@merit.edu
In-reply-to: <14730.53112.736182.535596@nodens.uraeus.com>
Date: Fri, 04 Aug 2000 08:01:27 -0700
Message-ID: <27673.965401287@ftel.net>
From: Mark Milhollan <mlm@ftel.net>
Errors-To: owner-nanog-outgoing@merit.edu
jmalcolm@uraeus.com writes:
>If you ask g about 'com', and instead of giving an answer like the one
>a.ROOT-SERVERS.NET gave you, it says it *does not exist*, you will,
>correctly, assume that means it doesn't exist and neither do any
>subdomains.
Currently G isn't answering queries, so it's not causing a problem.
A.ROOT-SERVERS.NET and H.ROOT-SERVERS.NET don't agree as to the minimum
TTL (518400 vs 172800), but that's not going to wreck anything.
>Hence, if you randomly query the one server that is returning NXDOMAIN
>for com, all com lookups will fail.
This is why BIND 8 has the bogus characteristic, or why one may need to
edit their root hint file. Too bad both require a reload/restart.
