On 27 Oct 2004, at 12:35, Stephane Bortzmeyer wrote:
On Fri, Sep 24, 2004 at 02:10:58PM -0400, Matt Larson <mlarson@verisign.com> wrote a message of 27 lines which said:
A few people have asked me privately to publish the IPv6 addresses ahead of time for reachability testing purposes, so here they are:
2001:503:a83e::2:30 (a.gtld-servers.net) 2001:503:231d::2:30 (b.gtld-servers.net)
Now that the IPv6 glues are published, I can not reach these nameservers from Renater:
In case more data points are required, neither of those servers are reachable from ISC. We appear to have no route for a.gtld-servers.net at all, and only a single path for b, which suggests some route propagation issues (we're well multi-homed in 3557; I'd expect to see lots of paths). Maybe Verisign needs more (reliable) v6 transit. [jabley@tag]% traceroute6 2001:503:a83e::2:30 traceroute6 to 2001:503:a83e::2:30 (2001:503:a83e::2:30) from 2001:4f8:4:d::236, 64 hops max, 12 byte packets 1 2001:4f8:4:d:290:6900:d32:a81f 0.669 ms !A 0.557 ms !A 0.441 ms !A [jabley@tag]% traceroute6 2001:503:231d::2:30 traceroute6 to 2001:503:231d::2:30 (2001:503:231d::2:30) from 2001:4f8:4:d::236, 64 hops max, 12 byte packets 1 2001:4f8:4:d:290:6900:d32:a81f 0.624 ms 0.573 ms 0.449 ms 2 fa-5-2.a01.snfcca05.us.ra.verio.net 0.550 ms 0.463 ms 0.417 ms 3 xe-1-2-0-4.r20.plalca01.us.bb.verio.net 1.728 ms 1.757 ms 1.688 ms 4 p16-0-1-3.r21.asbnva01.us.bb.verio.net 62.086 ms 62.145 ms 62.046 ms 5 p16-4-0-0.r02.asbnva01.us.bb.verio.net 62.191 ms 62.166 ms 62.228 ms 6 fa-0-1-1.r00.asbnva01.us.b6.verio.net 62.316 ms 62.289 ms 62.218 ms 7 verio-gw.mdtnj.ipv6.att.net 73.927 ms 73.587 ms 74.037 ms 8 * *^C [jabley@tag]% dig @2001:503:a83e::2:30 com soa ; <<>> DiG 8.3 <<>> @2001:503:a83e::2:30 com soa ; (1 server found) ;; res options: init recurs defnam dnsrch ;; res_nsend: Connection refused [jabley@tag]% dig @2001:503:231d::2:30 com soa ; <<>> DiG 8.3 <<>> @2001:503:231d::2:30 com soa ; (1 server found) ;; res options: init recurs defnam dnsrch ;; res_nsend: Operation timed out [jabley@tag]%
Filtering of the micro-allocation of the /48? Something else?
That's not our problem; we see the route to 2001:503:231d::/48 just fine, for example: jabley@r2.sfo2> show route 2001:503:a83e::2:30 jabley@r2.sfo2> show route 2001:503:231d::2:30 inet6.0: 761 destinations, 1748 routes (759 active, 0 holddown, 21 hidden) + = Active Route, - = Last Active, * = Both 2001:503:231d::/48 *[BGP/170] 00:49:51, MED 0, localpref 100 AS path: 2914 7018 26415 I > to 2001:418:1c00:5000::1 via ge-0/1/0.63 [BGP/170] 00:49:51, MED 0, localpref 100, from 2001:4f8:4::3 AS path: 2914 7018 26415 I to fe80::2a0:a5ff:fe12:caf via so-0/0/0.0 > to fe80::2a0:a5ff:fe12:caf via so-1/0/0.0 jabley@r2.sfo2> Joe