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!)
I think the last line of my traceroute is instructive: traceroute 198.41.0.4 traceroute to 198.41.0.4 (198.41.0.4), 30 hops max, 40 byte packets 1 cr1-hfc2.vista1.sdca.home.net (24.0.178.1) 17.192 ms 21.047 ms 18.722 ms 2 10.0.219.1 (10.0.219.1) 9.061 ms 16.608 ms 5.648 ms ... 15 a.root-servers.net (198.41.0.4) 104.697 ms bip1.internic.net (198.41.0.24) 151.400 ms 100.606 ms 198.41.0.4, 198.41.0.24 can you say whoops! I knew you could... sigh. -dave
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!)
On Wed, 26 Aug 1998, Richard Irving wrote:
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!)
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
On Wed, 26 Aug 1998, Richard Irving wrote:
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
--- The following sentence is false The preceding sentence is true
participants (4)
-
Bill Becker -
Chris Cappuccio -
David Schiffrin -
Richard Irving