Urrr... A-root server foul ?

Mailman List Mirror (Read Only)
1

Is anyone else seeing this ? really *cool* udp trick,
or is bcast space now DNS capable ? What am I missing ?

Server: ns2.mci.net
Address: 204.70.57.242

Non-authoritative answer:
Name: A.ROOT-SERVERS.NET
Address: 198.41.0.4

And a ping yields ?

64 bytes from 198.41.0.4: icmp_seq=16 ttl=250 time=59 ms
64 bytes from 198.41.0.4: icmp_seq=16 ttl=249 time=76 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=16 ttl=250 time=77 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=17 ttl=250 time=57 ms
64 bytes from 198.41.0.4: icmp_seq=17 ttl=250 time=64 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=17 ttl=249 time=73 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=18 ttl=250 time=71 ms
64 bytes from 198.41.0.4: icmp_seq=19 ttl=250 time=53 ms
64 bytes from 198.41.0.4: icmp_seq=19 ttl=249 time=57 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=19 ttl=249 time=73 ms (DUP!)

2

Is anyone else seeing this?

Yep, once you point us in that direction.

really *cool* udp trick, or is bcast space now DNS capable?
What am I missing?

198.41.0.4 can as far as I can see not be a broadcast address
under any left-contiguous netmask, unless it's the 0'th address
on some subnet and the router sitting on the net has the really-
old-style-and-now-deprecated directed broadcast address
forwarding enabled (not likely).

A DNS query to 198.41.0.4 does however only elicit a single
response, so I doubt this is much to worry about. (My guess:
they have 4 machines sharing the load via some form of load-
sharing setup.)

- H�vard

3

Interesting TTLs on those.

I'm getting four for the price of one...

biteme:~$ ping a.root-servers.net
PING a.root-servers.net (198.41.0.4): 56 data bytes
64 bytes from 198.41.0.4: icmp_seq=0 ttl=242 time=76.6 ms
64 bytes from 198.41.0.4: icmp_seq=0 ttl=243 time=94.1 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=0 ttl=243 time=106.0 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=0 ttl=242 time=126.0 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=1 ttl=243 time=85.0 ms
64 bytes from 198.41.0.4: icmp_seq=1 ttl=243 time=93.5 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=1 ttl=242 time=106.0 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=1 ttl=242 time=115.1 ms (DUP!)

Bill

4

Is anyone else seeing this ? really *cool* udp trick,
or is bcast space now DNS capable ? What am I missing ?

Server: ns2.mci.net
Address: 204.70.57.242

Non-authoritative answer:
Name: A.ROOT-SERVERS.NET
Address: 198.41.0.4

And a ping yields ?

64 bytes from 198.41.0.4: icmp_seq=16 ttl=250 time=59 ms
64 bytes from 198.41.0.4: icmp_seq=16 ttl=249 time=76 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=16 ttl=250 time=77 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=17 ttl=250 time=57 ms
64 bytes from 198.41.0.4: icmp_seq=17 ttl=250 time=64 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=17 ttl=249 time=73 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=18 ttl=250 time=71 ms
64 bytes from 198.41.0.4: icmp_seq=19 ttl=250 time=53 ms
64 bytes from 198.41.0.4: icmp_seq=19 ttl=249 time=57 ms (DUP!)
64 bytes from 198.41.0.4: icmp_seq=19 ttl=249 time=73 ms (DUP!)

Actually, let's use 12.7.96.0/24 as an example...

12.7.96.6 is the only machine in this range that has an answer on port 53
for DNS

empnet:chris {104} nslookup
Default Server: mimosa.noc.empnet.com
Address: 12.7.96.6

server 12.7.96.255

Default Server: [12.7.96.255]
Address: 12.7.96.255

merit.edu

Server: [12.7.96.255]
Address: 12.7.96.255

Non-authoritative answer:
Name: merit.edu
Address: 198.108.1.42