ICANN registrar supporting v6 glue?

Fri Jun 29 16:40:14 UTC 2007

> One note here is that even though you can get glue into com/net/org
> using this method, there is no IPv6 glue for the root yet, as such  
> even
> if you manage to get the IPv6 glue in, it won't accomplish much  
> (except
> sending all IPv6 capable resolvers over IPv6 transport :) as all

Unless I did this query wrong, you are absolutely right:

;.                              IN      NS
A.ROOT-SERVERS.NET.     3600000 IN      A       198.41.0.4
B.ROOT-SERVERS.NET.     3600000 IN      A       192.228.79.201
C.ROOT-SERVERS.NET.     3600000 IN      A       192.33.4.12
D.ROOT-SERVERS.NET.     3600000 IN      A       128.8.10.90
E.ROOT-SERVERS.NET.     3600000 IN      A       192.203.230.10
F.ROOT-SERVERS.NET.     3600000 IN      A       192.5.5.241
G.ROOT-SERVERS.NET.     3600000 IN      A       192.112.36.4
H.ROOT-SERVERS.NET.     3600000 IN      A       128.63.2.53
I.ROOT-SERVERS.NET.     3600000 IN      A       192.36.148.17
J.ROOT-SERVERS.NET.     3600000 IN      A       192.58.128.30
K.ROOT-SERVERS.NET.     3600000 IN      A       193.0.14.129
L.ROOT-SERVERS.NET.     3600000 IN      A       198.32.64.12
M.ROOT-SERVERS.NET.     3600000 IN      A       202.12.27.33

I don't see any v6 glue there...  Rather than having conversations  
about transition to IPv6, maybe we should be sure it works natively  
first?  It's rather ironic to think that for v6 DNS to work an  
incumbent legacy protocol is still required.  The GTLD's appear to  
have somewhat better v6 services than root:

A.GTLD-SERVERS.NET.     172800  IN      AAAA    2001:503:a83e::2:30
B.GTLD-SERVERS.NET.     172800  IN      AAAA    2001:503:231d::2:30

I'm pretty disappointed now,

-Barrett