It's 2018 and still no IPv6 by default?



According to this post there were plans to enable IPv6 by default back in 2017. As far as I can tell the change never occurred. The only domains that are serving IPv6 are 2.< name > domains.

Any idea why the change was never implemented?


Hi @imcdona

Mostly just that I haven’t gotten around to do the work to generate the zones in a smarter way to handle the underserved ones. I don’t want to make the service worse by serving the clients AAAA records if there aren’t enough IPv6 servers but would have been enough IPv4 servers, for example.


@ask That makes sense. I’m curious though, how are you going to determine the demand for IPv6 NTP servers without actually making the switch? Do you have DNS stats that indicate the number of requests for AAAA records on the the primary zones?


Maybe we can start testing by zones with more ipv6 servers than ipv4 servers, like tw zone. :sweat_smile:


Even in Q4 2018 I wouldn’t expect majority of queries come over IPv6:
Right now one of my CZ servers is getting around 700qps over IPv4 and 50qps over IPv6.


In fact some tw servers are mis-categorized hence reducing tw zone capacity. Some guy (maybe) inside Yahoo! registered these servers, but the ipv4 address of and are both categorized as from sg. You can confirm this by traceroute through Hinet, largest ISP in Taiwan. Correct this and the poor tw zone will become healthier.


I have two servers (mistakenly categorized under CN zone). Each gets between 200-1500 qps over IPv6. Seems to me though IPv6 adoption is pretty low in Asia percentage wise, the sheer amount of computers still makes the qps looks significant.