[52449] in North American Network Operators' Group

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

Re: Root DNS Server Issues?

daemon@ATHENA.MIT.EDU (John M. Brown)
Tue Oct 1 23:12:56 2002

Date: Tue, 1 Oct 2002 20:12:14 -0700
From: "John M. Brown" <john@chagresventures.com>
To: Valdis.Kletnieks@vt.edu
Cc: nanog@merit.edu
In-Reply-To: <200210020241.g922f9Jf006279@turing-police.cc.vt.edu>; from Valdis.Kletnieks@vt.edu on Tue, Oct 01, 2002 at 10:41:09PM -0400
Errors-To: owner-nanog-outgoing@merit.edu


add  www.  to the zone and look for a A RR.
then look up the A RR on one of ultra's servers

Rodney's point is that the gTLD servers have bad glue data and its a
PIA to get that data changed.

Some folks also place www.example.com  as a NS so that it will be glue and
thus provide faster look up times for all those wonderful metric programs
that say how wonderful you are.



On Tue, Oct 01, 2002 at 10:41:09PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 01 Oct 2002 17:11:00 PDT, Rodney Joffe <rjoffe@centergate.com>  said:
> 
> > [rjoffe@layer9 rjoffe]$ dig @a.gtld-servers.net www.tombannenchev.com
> 
> Well... a.gtld-servers.net isn't a root server (got bit by that myself a
> while ago ;) and even then...
> 
> > tombannenchev.com.      172800  IN      NS      UDNS1.ULTRADNS.NET.
> > tombannenchev.com.      172800  IN      NS      UDNS2.ULTRADNS.NET.
> 
> It doesn't resolve it, it just gives you 2 NS records..
> 
> > [rjoffe@layer9 rjoffe]$ dig @udns1.ultradns.net www.tombannenchev.com
> 
> Which finally resolves it...



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