Re: Hidden name servers?

["Wojtek Zlobicki" <wojtekz () idirect com>]

I decided to do some RADB queries on the new dns server. Lo and behold,
different subnets and differents AS #'s for each.  I guess Microsoft has
learned a little from this experience.

RADB Whois query for 216.32.118.104

route:         216.32.96.0/19
descr:         NET-EXODUS-SantaClara
origin:        AS3967
mnt-by:        MAINT-AS3967
changed:       radb () bengi exodus net 19990322
source:        RADB

RADB Whois query for 32.96.80.17
route:         32.96.0.0/16
descr:         IBM Global Services
origin:        AS2685
member-of:     RS-COMM_NSFNET
mnt-by:        MAINT-AS2685
changed:       pdsides () us ibm com 19980826
source:        RADB

RADB Whois query for 207.229.152.20


route:         207.229.128.0/18
descr:         EnterAct Corp.
               407 S. Dearborn St.
               Floor 6
               Chicago, IL 60605
origin:        AS6555
mnt-by:        MAINT-AS6555
changed:       ablake () enteract com 19990725
source:        RADB

RADB Whois query for 213.161.66.158


route:              213.161.64.0/19
descr:              AboveNet
origin:             AS6461
mnt-by:             MAINT-AS6461
changed:            yifun () above net 20001214
source:             RADB

----- Original Message -----
From: "Greg A. Woods" <woods () weird com>
To: "Sean Donelan" <sean () donelan com>
Cc: <nanog () merit edu>
Sent: Saturday, January 27, 2001 5:21 PM
Subject: Re: Hidden name servers?


> [ On , January 26, 2001 at 23:28:06 (-0800), Sean Donelan wrote: ]
> > Subject: Hidden name servers?
> >
> > How do I get name servers added to the COM TLD zone file which
> > are not listed in the NSI Registry WHOIS database?
>
> Be careful where you query.  There's not necessarily any relationship to
> the times when the NSI WHOIS database is updated and the times when the
> gTLD servers are updated.
>
> The new NS records are in the right place now:
>
> $ host -r -Z -t ns microsoft.com a.root-servers.net
> microsoft.com.          172800  IN      NS      DNS4.CP.MSFT.NET.
> microsoft.com.          172800  IN      NS      DNS5.CP.MSFT.NET.
> microsoft.com.          172800  IN      NS      DNS7.CP.MSFT.NET.
> microsoft.com.          172800  IN      NS      DNS6.CP.MSFT.NET.
> microsoft.com.          172800  IN      NS      Z1.MSFT.AKADNS.COM.
> microsoft.com.          172800  IN      NS      Z2.MSFT.AKADNS.COM.
> microsoft.com.          172800  IN      NS      Z6.MSFT.AKADNS.COM.
> microsoft.com.          172800  IN      NS      Z7.MSFT.AKADNS.COM.
>
>
> In any case it is possible to list additional NS records in your zone in
> order to achive higher reliability for your DNS in the case where the
> registered servers are only intermittently available....  Note that this
> doesn't help for long if the registered servers are totally unreachable
> for longer than the TTL on the additional un-registered NS records.
>
> --
> Greg A. Woods
>
> +1 416 218-0098      VE3TCP      <gwoods () acm org>      <robohack!woods>
> Planix, Inc. <woods () planix com>; Secrets of the Weird <woods () weird com>