Ew, gerbilcenter..
;; ANSWER SECTION:
k.gtld-servers.net. 3d9h11m26s IN A 195.8.99.11
inetnum: 195.8.98.0 - 195.8.99.255
netname: ISI-NET-LHR2-A
descr: Frontier GlobalCenter (formerly Internet Systems)
descr: Internet Service Provider (GB)
-->
I find it ironic and humorous that a gtld-servers.net machine has
no in-addr.arpa records.
; <<>> DiG 8.1 <<>> 11.99.8.195.in-addr.arpa. ptr
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6
195.IN-ADDR.ARPA. 9m2s IN SOA ns.ripe.net. ops.ripe.net. (
heh.
nsi strikes again.
good show.
David H. Holtzman wrote:
Is GlobalCenter the intended location of the K.GTLD-SERVERS.NET?
What was wrong with the LINX service network where the
K.ROOT-SERVERS.NET is installed?
When K.ROOT-SERVERS.NET was moved to London, we invested some effort
to optimize routing towards the LINX from the European research
networks. Is the plan that we do this again for the new gTLD server?
Right now a query/response to the new gTLD server in England takes
four transatlantic hops from Switzerland. I don't really see the
improvement with respect to the other name servers, except for those
who peer with GlobalCenter in Europe.
$ ping -sv k.gtld-servers.net. 140 10
PING k.gtld-servers.net: 140 data bytes
148 bytes from 195.8.99.11: icmp_seq=1. time=239. ms
148 bytes from 195.8.99.11: icmp_seq=2. time=308. ms
148 bytes from 195.8.99.11: icmp_seq=3. time=437. ms
148 bytes from 195.8.99.11: icmp_seq=4. time=466. ms
148 bytes from 195.8.99.11: icmp_seq=6. time=442. ms
148 bytes from 195.8.99.11: icmp_seq=7. time=456. ms
148 bytes from 195.8.99.11: icmp_seq=8. time=467. ms
----k.gtld-servers.net PING Statistics----
10 packets transmitted, 7 packets received, 30% packet loss
round-trip (ms) min/avg/max = 239/402/467
$ ping -sv k.root-servers.net. 140 10
PING k.root-servers.net: 140 data bytes
148 bytes from k.root-servers.net (193.0.14.129): icmp_seq=0. time=39. ms
148 bytes from k.root-servers.net (193.0.14.129): icmp_seq=1. time=41. ms
148 bytes from k.root-servers.net (193.0.14.129): icmp_seq=2. time=44. ms
148 bytes from k.root-servers.net (193.0.14.129): icmp_seq=3. time=38. ms
148 bytes from k.root-servers.net (193.0.14.129): icmp_seq=4. time=36. ms
148 bytes from k.root-servers.net (193.0.14.129): icmp_seq=5. time=52. ms
148 bytes from k.root-servers.net (193.0.14.129): icmp_seq=6. time=46. ms
148 bytes from k.root-servers.net (193.0.14.129): icmp_seq=7. time=40. ms
148 bytes from k.root-servers.net (193.0.14.129): icmp_seq=8. time=34. ms
148 bytes from k.root-servers.net (193.0.14.129): icmp_seq=9. time=35. ms
----k.root-servers.net PING Statistics----
10 packets transmitted, 10 packets received, 0% packet loss
round-trip (ms) min/avg/max = 34/40/52
Regards,
For the record: k.root-servers.net is housed by the LINX and operated by
the RIPE NCC under the authority of IANA. Its deployment has been
subject to considerable coordination efforts.
gTLD servers are operated under the authority of the gTLD administrators
concerned. When the k.root-servers.net was installed an offer was
extended to NSI for the housing of a gtld server at the Linx
under arrangements similar to k.root-servers.net with the server
operated by a third party.
Daniel