Re: Poor connectivity to new b.root-servers.net address?

[sthaug () nethelp no]

>    the problem seems to be in the level3/cenic/losnettos path.
>  
>    juniper -ge- gsr -ge- foundary -ge- foundary -ge- foundary -100m- 7513
>
>    the IP path is:
>
>       juniper - 7513
>
>    more as we unearth the problems... 

What I didn't mention in my original post is that this problem has
existed, as far as I can see, since B was moved to a new address.

Anyway - it seems things are fixed now. DNS lookup, traceroute and
ping work from AS 2116 (source address 193.71.2.2) and AS 3307 (source
address 194.19.15.2).

There are still timeouts at the router hop before 130.152.181.66, which
looks like it should be 67.30.130.66, traceroute'ing from 193.71.2.2 and
194.19.15.2:

13  so-10-0.hsa1.Tustin1.Level3.net (209.244.27.154)  188.092 ms so-9-0.hsa1.Tustin1.Level3.net (209.244.27.174)  
188.118 ms  187.955 ms
14  * * *
15  130.152.181.66 (130.152.181.66)  177.112 ms  177.141 ms  177.202 ms

and

13  so-11-0.hsa1.Tustin1.Level3.net (209.244.27.162)  188.861 ms  188.604 ms so-8-0.hsa1.Tustin1.Level3.net 
(209.244.27.166)  188.947 ms
14  * * *
15  130.152.181.66 (130.152.181.66)  187.970 ms  187.573 ms  187.399 ms

The missing hop here is visible as 67.30.130.66 coming from 129.241.1.16
(AS 224).

I'm not going to worry too much about the traceroute timeouts, even if
it would be nice if that could also be fixed. The main point is that DNS
lookups are now working as they should. Thanks!

Steinar Haug, Nethelp consulting, sthaug () nethelp no