From where I sit, it looks like:
a.root-servers.net has IPv6 address 2001:503:ba3e::2:30
BGP routing table entry for 2001:503:ba3e::/48
f.root-servers.net has IPv6 address 2001:500:2f::f
BGP routing table entry for 2001:500:2f::/48
h.root-servers.net has IPv6 address 2001:500:1::803f:235
BGP routing table entry for 2001:500:1::/48
j.root-servers.net has IPv6 address 2001:503:c27::2:30
BGP routing table entry for 2001:503:c27::/48
k.root-servers.net has IPv6 address 2001:7fd::1
BGP routing table entry for 2001:7fd::/32
l.root-servers.net has IPv6 address 2001:500:3::42
BGP routing table entry for 2001:500:3::/48
m.root-servers.net has IPv6 address 2001:dc3::35
BGP routing table entry for 2001:dc3::/32
b.root-servers.net has no AAAA record
c.root-servers.net has no AAAA record
d.root-servers.net has no AAAA record
e.root-servers.net has no AAAA record
g.root-servers.net has no AAAA record
i.root-servers.net has no AAAA record
So... Likely, Verizon customers can reach k and m root servers via IPv6
and not the others.
The fact that b, c, d, e, g, and i do not have AAAA records actually
concerns me
more than the fact that Verizon customers can only reach two.
Owen
On Oct 12, 2009, at 4:39 PM, Nathan Ward wrote:
On 13/10/2009, at 8:26, Jeff McAdams <je...@iglou.com> wrote:
Verizon's policy has been related to me that they will not accept
or propogate any IPv6 route advertisements with prefix lengths
longer than /32. Full stop. So that even includes those of us
that have /48 PI space from ARIN that are direct customers of
Verizon.
What about the small matter of all of the current AAAAs for the the
IPv6 enabled root DNS servers?
--
Nathan Ward
