North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: Poor connectivity to new b.root-servers.net address?
> 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 126.96.36.199) and AS 3307 (source address 188.8.131.52). There are still timeouts at the router hop before 184.108.40.206, which looks like it should be 220.127.116.11, traceroute'ing from 18.104.22.168 and 22.214.171.124: 13 so-10-0.hsa1.Tustin1.Level3.net (126.96.36.199) 188.092 ms so-9-0.hsa1.Tustin1.Level3.net (188.8.131.52) 188.118 ms 187.955 ms 14 * * * 15 184.108.40.206 (220.127.116.11) 177.112 ms 177.141 ms 177.202 ms and 13 so-11-0.hsa1.Tustin1.Level3.net (18.104.22.168) 188.861 ms 188.604 ms so-8-0.hsa1.Tustin1.Level3.net (22.214.171.124) 188.947 ms 14 * * * 15 126.96.36.199 (188.8.131.52) 187.970 ms 187.573 ms 187.399 ms The missing hop here is visible as 184.108.40.206 coming from 220.127.116.11 (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, [email protected]