[4492] in testers

home help back first fref pref prev next nref lref last post

Re: named oddness

daemon@ATHENA.MIT.EDU (Thomas Bushnell, BSG)
Thu Jun 22 08:05:46 2000

To: John Hawkinson <jhawk@MIT.EDU>
Cc: testers@MIT.EDU
From: tb@MIT.EDU (Thomas Bushnell, BSG)
Date: 22 Jun 2000 08:05:39 -0400
In-Reply-To: John Hawkinson's message of "Thu, 22 Jun 2000 07:41:05 -0400 (EDT)"
Message-ID: <u1h66r19azw.fsf@oliver.mit.edu>

John Hawkinson <jhawk@MIT.EDU> writes:

> 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.
>
> [...]
> 
> 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...

I experienced similar symptoms on oliver; once looking up
www.microsoft.com, and once looking up www.ship-of-fools.com.  I got
name resolution errors from multiple clients.  I did not experiment
with named caches, but on both occurrences the problem vanished upon
restarting named.

If the problem is local to us, then it's not specifically
Sun-specific.


home help back first fref pref prev next nref lref last post