Tony, Tony Finch: > Joe Abley <jab...@hopcount.ca> wrote: >> >> There are potentially 249 TLDs that are not operated under any such >> contract with ICANN, although I agree that the majority of ccTLDs have >> at least one nameserver that is v6-capable (maybe all, but I haven't >> checked and I wouldn't want to assume). > > Quick root zone stats: > > zones 1542 > servers 4216 > > Most servers are dual-stacked; 539 are v4-only, and 2 are v6-only > (j.zdnscloud.com and i.zdnscloud.com). > > The 31 TLDs with no v6 nameservers: > > ai. [ snippity ] > zw.
Your list is missing bf., which does not appear to have any IPv6 name servers right now. It also counts quite a few more than my checks: gf. mq. mh. mv. ni. xn--lgbbat1ad8j. ye. zw. I'm not sure what your methodology is exactly, but I put mine on GitHub: https://github.com/shane-kerr/tldIPv6 My guess is that you just looked at the root zone itself, since I see that bf. has IPv6 glue: ;; AUTHORITY SECTION: bf. 172800 IN NS nahouri.onatel.bf. bf. 172800 IN NS ns-bf.afrinic.net. bf. 172800 IN NS censvrns0001.ird.fr. ;; ADDITIONAL SECTION: ns-bf.afrinic.net. 172800 IN AAAA 2001:43f8:120::34 nahouri.onatel.bf. 172800 IN A 206.82.130.196 ns-bf.afrinic.net. 172800 IN A 196.216.168.34 censvrns0001.ird.fr. 172800 IN A 91.203.32.147 Whereas zw. does not: zw. 172800 IN NS ns2.telone.co.zw. zw. 172800 IN NS ns3.telone.co.zw. zw. 172800 IN NS ns2.gip.net. zw. 172800 IN NS ns1.telone.co.zw. ;; ADDITIONAL SECTION: ns1.telone.co.zw. 172800 IN A 194.133.122.47 ns2.gip.net. 172800 IN A 204.59.1.222 ns2.telone.co.zw. 172800 IN A 194.133.122.42 ns3.telone.co.zw. 172800 IN A 194.133.122.34 Probably I should update my code to *ALSO* check whether or not a zone has some usable IPv6 path either through glue or a name server under a TLD that supports IPv6. I suppose it can verify glue at the same time. (I'm not sure what happens in a resolver to a zone like bf., when below the zone cut IPv6 is *not* supported but above the zone cut it *is*, due to mismatched glue.) Cheers, -- Shane _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
