Simon Waters wrote:
NANOG Digest wrote:
13 so-10-0.hsa1.Tustin1.Level3.net (209.244.27.154) 178.710 ms 178.529 ms 178.500 ms 14 * * * 15 130.152.181.66 (130.152.181.66) 177.340 ms 177.246 ms 177.298 ms 16 * * *
I see something similar to this coming out of Level3 from Demon's direction.
The was mentioned in comp.protocols.dns.bind, where some additional traceroutes and information is available, although it is clearly(?) a routing issue and I suggested here was a good place to ask for help.
Still we have enough root servers to be going on with while it is fixed, lets just hope no one hijacked it.
Looks OK from SURFnet (AS1103) through Level3:
[...]
13 so-11-0.hsa1.Tustin1.Level3.net (209.244.27.162) 165.036 ms 165.507 ms 162.457 ms
14 67.30.130.66 (67.30.130.66) 176.217 ms 176.318 ms 176.135 ms
15 130.152.181.66 (130.152.181.66) 175.381 ms 177.407 ms 175.566 ms
16 b.root-servers.net (192.228.79.201) [open] 179.704 ms 174.683 ms 180.950 ms
__
Erik-Jan.
