Re: SERVER NAMES

[Alex Rubenstein <alex () nac net>]

because of a firewall at Bellcore, I can't tell if this is the case.

However, it should be noted that just because two nameservers share a /24,
doesn't mean they are located at the same facility:


traceroute to ns1.nac.net (207.99.0.1), 30 hops max, 40 byte packets
 1  f0-0-1.colo1.oct.nac.net (209.123.109.1)  0.778 ms  0.764 ms  0.705 ms
 2  ns1 (207.99.0.1)  0.511 ms  0.507 ms  0.436 ms


traceroute to ns2.nac.net (207.99.0.2), 30 hops max, 40 byte packets
 1  f0-0-1.colo1.oct.nac.net (209.123.109.1)  0.709 ms  0.969 ms  0.701 ms
 2  f4-1-0-1.core2.oct.nac.net (209.123.168.225)  0.948 ms  0.708 ms 0.721 ms
 3  s5-1.core1.nyc.nac.net (209.123.11.222)  7.275 ms  6.214 ms  2.900 ms
 4  ns2 (207.99.0.2)  5.116 ms  10.012 ms  4.200 ms



On Thu, 3 Feb 2000, Majdi Abbas wrote:

> > At the risk of suggesting that Bellcore solved the problem, aren't 
> > there some prevailing standards here?
>
>    Domain servers in listed order:
>
>    DNS.BELLCORE.COM             128.96.41.3
>    NS.BELLCORE.COM              128.96.41.1
>    NS.USWEST.COM                130.13.16.6
>
>       Apparently not.
>
>       -and- their nameservers are in the same netblock.
>
>       --msa