[afnog] Concern about gTLD servers

[Alex Kamiru]

Actually, the 17ms is for l root, I guess the com and net are no longer 
active.

On 03/10/2012 04:07 PM, Alex Kamiru wrote:
> KE IXP has always had .com and .net instances. My response for .net 
> shows 17ms
>
> dig +trace verizon.net
>
> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5_7.1 <<>> +trace verizon.net
> ;; global options:  printcmd
> .            331894    IN    NS    l.root-servers.net.
> .            331894    IN    NS    d.root-servers.net.
> .            331894    IN    NS    b.root-servers.net.
> .            331894    IN    NS    i.root-servers.net.
> .            331894    IN    NS    k.root-servers.net.
> .            331894    IN    NS    g.root-servers.net.
> .            331894    IN    NS    h.root-servers.net.
> .            331894    IN    NS    f.root-servers.net.
> .            331894    IN    NS    e.root-servers.net.
> .            331894    IN    NS    a.root-servers.net.
> .            331894    IN    NS    m.root-servers.net.
> .            331894    IN    NS    c.root-servers.net.
> .            331894    IN    NS    j.root-servers.net.
> ;; Received 512 bytes from 41.203.208.18#53(41.203.208.18) in 1 ms
>
> net.            172800    IN    NS    a.gtld-servers.net.
> net.            172800    IN    NS    b.gtld-servers.net.
> net.            172800    IN    NS    c.gtld-servers.net.
> net.            172800    IN    NS    d.gtld-servers.net.
> net.            172800    IN    NS    e.gtld-servers.net.
> net.            172800    IN    NS    f.gtld-servers.net.
> net.            172800    IN    NS    g.gtld-servers.net.
> net.            172800    IN    NS    h.gtld-servers.net.
> net.            172800    IN    NS    i.gtld-servers.net.
> net.            172800    IN    NS    j.gtld-servers.net.
> net.            172800    IN    NS    k.gtld-servers.net.
> net.            172800    IN    NS    l.gtld-servers.net.
> net.            172800    IN    NS    m.gtld-servers.net.
> ;; Received 486 bytes from 199.7.83.42#53(l.root-servers.net) in 17 ms
>
> verizon.net.        172800    IN    NS    ns2.verizon.net.
> verizon.net.        172800    IN    NS    ns4.verizon.net.
> verizon.net.        172800    IN    NS    ns5.verizon.net.
> verizon.net.        172800    IN    NS    ns6.verizon.net.
> verizon.net.        172800    IN    NS    ns1.verizon.net.
> verizon.net.        172800    IN    NS    ns3.verizon.net.
> ;; Received 233 bytes from 192.5.6.30#53(a.gtld-servers.net) in 284 ms
>
> verizon.net.        300    IN    A    206.46.232.39
> verizon.net.        86400    IN    NS    ns4.verizon.net.
> verizon.net.        86400    IN    NS    ns1.verizon.net.
> verizon.net.        86400    IN    NS    ns2.verizon.net.
> verizon.net.        86400    IN    NS    ns3.verizon.net.
> ;; Received 181 bytes from 151.203.0.86#53(ns2.verizon.net) in 217 ms
>
>
>
>
> On 03/10/2012 01:56 PM, Graham Beneke wrote:
>> This discussion popped up on NANOG this morning and its relevant to 
>> the AfNOG community:
>>
>> On 10/03/2012 09:22, Frank Habicht wrote:
>>> On 3/10/2012 10:12 AM, Randy Bush wrote:
>>>>> This problem is unfortunately not unique to India. There appear to 
>>>>> be no
>>>>> anycast instances of the gTLD servers in Africa either.
>>>>
>>>> really!?
>>>
>>> There was one in KE but can't find or reach it:
>>> [a-m].gtld-servers.net.  seem all to be in 192.0.0.0/8
>>>
>>> route-views.kixp.routeviews.org>  sh ip bgp 192.0.0.0/8 lo
>>> route-views.kixp.routeviews.org>
>>>
>>> Likely there is still (?) in EG ...?
>>
>> Is anyone aware of any working instances of the gTLD servers in Africa?
>>
>
>
> _______________________________________________
> afnog mailing list
> http://afnog.org/mailman/listinfo/afnog
>