Hi Matjaz,
We contacted also one of our upstream provider (same as you: GEANT)
Qwest and HE. It turned out combined effort had a resolution.
Thanks,
Janos Mohacsi
Head of HBONE+ project
Network Engineer, Director Network and Multimedia
NIIF/HUNGARNET, HUNGARY
Co-chair of Hungarian IPv6 Forum
Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300 6F64 7B00 70EF 9882
On Wed, 12 Jun 2013, Matjaž Straus Istenič wrote:
Dear Janos,
we (AS2107) have experienced same problems on the route with AS_PATH
20965/GEANT 6939/HE 209/Qwest 26496/GoDaddy. If we send traffic directly
via Level3 (AS_PATH 3356/Level3 26496/GoDaddy or even 20965/GEANT
3356/Level3 26496/GoDaddy) it works fine. Hope this information will be
valuable to you.
Kind regards,
Matjaž
On 12. jun. 2013, at 16:49, Mohacsi Janos <[email protected]> wrote:
Dear All,
from our AS1955, and part of the Internet(according to different looking
glasses) GoDaddy IPv6 nameservers are not reachable.
dns03.domaincontrol.com. AAAA 2607:f208:207::33
pdns04.domaincontrol.com. AAAA 2607:f208:303::33
RP/0/RSP0/CPU0:rtr1.vh#traceroute 2607:f208:207::33 Tue Jun 11 15:04:17.907 CEST
Type escape sequence to abort.
Tracing the route to 2607:f208:207::33
1 2001:798:1b:10aa::5 2 msec 1 msec 0 msec
2 2001:798:cc:1b01:1b01::1 1 msec 1 msec 0 msec
3 2001:798:cc:3301:1b01::5 3 msec 7 msec 3 msec
4 2001:798:cc:1301:3301::1 7 msec 7 msec 7 msec
5 2001:798:cc:1301:1401::6 13 msec 14 msec 13 msec
6 2001:7f8::1b1b:0:1 19 msec 19 msec 25 msec
7 2001:470:0:1d4::2 28 msec 37 msec 28 msec
8 2001:470:0:1b1::1 115 msec 126 msec 114 msec
9 2001:504:0:2::209:1 112 msec 112 msec 145 msec
10 2001:428::205:171:2:213 194 msec 193 msec 192 msec
11 2001:428:5802:10::2 183 msec 183 msec 183 msec
12 ? * ?
13 * * ?
14 * * *
15 * *
From RIPE NCC:
traceroute to 2607:f208:207::33 (2607:f208:207::33), 30 hops max, 40 byte
packets
1 gw.ipv6.dev.nikrtr.ripe.net (2001:67c:2e8:2::1:1) 0.432 ms 0.411 ms 0.428
ms
2 amsix-501.xe-0-0-0.jun1.bit-1.network.bit.nl (2001:7f8:1::a501:2859:2) 2.306
ms 2.345 ms 2.324 ms
3 805.ge-0-0-0.jun1.thn.network.bit.nl (2001:7b8:0:325::2) 24.777 ms 24.388
ms 24.756 ms
4 * * *
5 * * *
Not from HE:
core1.fmt1.he.net> traceroute ipv6 2607:f208:207::33
Tracing the route to IPv6 node 2607:f208:207::33 from 1 to 30 hops
1 22 ms 7 ms <1 ms 2001:470:0:2d::2
2 18 ms 104 ms 20 ms 2001:470:0:18d::2
3 9 ms 39 ms 25 ms 2001:504:0:3::209:1
4 24 ms 47 ms 27 ms 2001:428::205:171:2:213
5 25 ms 37 ms 37 ms 2001:428:5802:10::2
6 * * * ?
7 * * * ?
8 * * * ?
9 * * * ?
However it is working from Nordunet:
traceroute6 to 2607:f208:207::33 (2607:f208:207::33) from 2001:6b0:1e:1::35, 64
hops max, 12 byte packets
1 t1fre-ae5-v1.sunet.se (2001:6b0:1e:1::36) 0.540 ms 0.476 ms 0.465 ms
2 se-fre.nordu.net (2001:948:0:f051::1) 0.383 ms 0.428 ms 0.377 ms
3 dk-ore.nordu.net (2001:948:1:2::3) 10.177 ms 9.782 ms 9.756 ms
4 uk-hex.nordu.net (2001:948:1:8::2) 39.687 ms 39.877 ms 36.170 ms
5 us-ash.nordu.net (2001:948:1:11::3) 112.198 ms 112.242 ms 112.165 ms
6 2001:504:0:2:0:2:6496:1 (2001:504:0:2:0:2:6496:1) 113.408 ms 113.278 ms
113.210 ms
7 2607:f208:3:100::1 (2607:f208:3:100::1) 113.022 ms 112.850 ms 131.426 ms
8 2607:f208:3:100::102 (2607:f208:3:100::102) 112.813 ms 112.697 ms 136.299
ms
9 2607:f208:3:100::102 (2607:f208:3:100::102) 119.837 ms !P 112.665 ms !P
112.754 ms !P
Can you help debugging where the routing is misconfgured?
thanks,
Janos Mohacsi
---
Matjaž Straus Istenič, Arnes
[email protected]
Tel: +386 1 4798877 Mob: +386 40 200403 Fax: +386 1 4798878
MS6745-RIPE
PGP 490F3B4F 2009-10-21
Fingerprint = 6172 7BF8 B0B7 1F09 47B3 AFA3 0946 1701 490F 3B4F
