[19116] in North American Network Operators' Group
Re: Urrr... A-root server foul ?
daemon@ATHENA.MIT.EDU (David Schiffrin)
Wed Aug 26 16:42:53 1998
From: David Schiffrin <daves@adnc.com>
To: rirving@onecall.net
Date: Wed, 26 Aug 1998 12:45:08 -0700 (PDT)
Cc: nanog@merit.edu
In-Reply-To: <35E46042.70735788@onecall.net> from "Richard Irving" at Aug 26, 98 02:21:38 pm
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!)
>
