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.
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
Hm - both through 3561 (CW) and 3549 (GBLX) in Europe (tracing from
source-IP's on our border routers from the respective providers'
netblocks, and our own IP's), we have no connectivity. Both paths go
via Level3.
/leg
Hi!
> 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:
Also some other traces, 2 broken, 1 ok:
[...]
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
From within AS8341, it looks broken. Following the same path, First CW
then L3. Have a look:
2 zar1-ge-2-1-0.Amsterdamamt.cw.net (208.173.220.113) 1.530 ms 1.442 ms 3.995 ms
3 zcr1-ge-2-1-0.Amsterdamamt.cw.net (208.173.220.129) 1.805 ms 1.800 ms 1.537 ms
4 so-4-3.core1.Amsterdam1.Level3.net (213.244.165.245) 1.908 ms 1.498 ms 1.537 ms
5 ae-0-55.mp1.Amsterdam1.Level3.net (213.244.165.97) 2.325 ms 2.287 ms 2.314 ms
6 so-1-0-0.mp1.London2.Level3.net (212.187.128.49) 9.523 ms 11.070 ms 9.718 ms
7 so-1-0-0.bbr1.Washington1.Level3.net (212.187.128.138) 82.906 ms 82.927 ms 82.773 ms
8 so-3-0-0.mpls1.Tustin1.Level3.net (209.247.8.121) 146.309 ms 147.126 ms 146.342 ms
9 so-9-0.hsa1.Tustin1.Level3.net (209.244.27.174) 146.259 ms so-10-0.hsa1.Tustin1.Level3.net (209.244.27.154) 146.659 ms 146.667 ms
10 * * *
11 130.152.181.66 (130.152.181.66) 149.828 ms 149.559 ms 149.154 ms
12 * * *
13 * * *
14 * * *
From AS24730, going over Verio and then L3 it looks like:
2 welcome-at-telecity2.as24730.net (81.23.229.130) 1.851 ms 2.075 ms 2.120 ms
3 81.20.69.105 (81.20.69.105) 2.260 ms 1.849 ms 2.206 ms
4 ge-1-1-0-4.r00.amstnl02.nl.bb.verio.net (81.20.65.134) 2.147 ms 2.211 ms 2.116 ms
5 so-4-1.core2.Amsterdam1.Level3.net (213.244.165.241) 1.863 ms 2.107 ms 2.101 ms
6 ae-0-55.mp1.Amsterdam1.Level3.net (213.244.165.97) 2.229 ms 2.688 ms 2.384 ms
7 so-1-0-0.mp1.London2.Level3.net (212.187.128.49) 10.619 ms 10.457 ms 10.469 ms
8 so-1-0-0.bbr1.Washington1.Level3.net (212.187.128.138) 83.346 ms 83.053 ms 83.520 ms
9 so-3-0-0.mpls1.Tustin1.Level3.net (209.247.8.121) 151.246 ms 150.947 ms 150.541 ms
10 so-9-0.hsa1.Tustin1.Level3.net (209.244.27.174) 150.845 ms 151.027 ms 151.037 ms
11 * * *
12 130.152.181.66 (130.152.181.66) 151.955 ms 151.945 ms 157.032 ms
13 * * *
14 * * *
15 * * *
If i do a AS12871 trace, going over interoute and then L3 its like:
2 e3-0-1-1.nikhef.concepts-ict.net (213.197.27.5) 3.673 ms 4.584 ms 3.204 ms
3 212.23.59.161 (212.23.59.161) 5.300 ms 3.891 ms 3.862 ms
4 PO6-0.Ams-Koo-core-2.interoute.net (212.23.41.145) 148.712 ms 164.519 ms 201.272 ms
5 PO9-1.Lon-Kie-core-1.interoute.net (212.23.41.154) 14.305 ms 13.069 ms 10.758 ms
6 PO1-0.lon-002-inter-1.interoute.net (212.23.41.34) 10.363 ms 11.566 ms 14.740 ms
7 sl-gw23-lon-5-1.sprintlink.net (213.206.157.9) 16.760 ms 10.517 ms 10.425 ms
8 sl-bb23-lon-8-0.sprintlink.net (213.206.128.62) 11.035 ms 11.007 ms 10.594 ms
9 sl-bb21-lon-13-0.sprintlink.net (213.206.128.55) 157.364 ms 194.912 ms 12.728 ms
10 213.206.131.22 (213.206.131.22) 13.609 ms 12.631 ms 14.197 ms
11 ae-0-51.mp1.London1.Level3.net (212.187.131.1) 12.682 ms 15.102 ms 12.724 ms
12 so-1-0-0.mp1.London2.Level3.net (212.187.128.49) 13.006 ms 17.141 ms 16.816 ms
13 so-1-0-0.bbr1.Washington1.Level3.net (212.187.128.138) 85.722 ms 85.054 ms 92.681 ms
14 so-3-0-0.mpls1.Tustin1.Level3.net (209.247.8.121) 150.560 ms 148.850 ms 149.794 ms
15 so-9-0.hsa1.Tustin1.Level3.net (209.244.27.174) 148.736 ms so-10-0.hsa1.Tustin1.Level3.net (209.244.27.154) 154.474 ms so-9-0.hsa1.Tustin1.Level3.net (209.244.27.174) 148.984 ms
16 67.30.130.66 (67.30.130.66) 151.593 ms 150.796 ms 150.023 ms
17 130.152.181.66 (130.152.181.66) 150.680 ms 152.805 ms 151.527 ms
18 b.root-servers.net (192.228.79.201) 157.921 ms 151.542 ms 157.816 ms
Hope this helps, its broken somewhere at the end for sure.
Bye,
Raymond.