You will be happy.
I made my 2 VPS-servers also use IPv6.
So my own pool ntp.heppen.be contain 4 servers where 2 are dual stack:
bas@workstation:~$ nslookup ntp.heppen.be
I forgot all about them having with IP6 DNS-records.
Hope you like it.
It would be even better though if @ask would add AAAA-records to all instances of the pool and not just the 2.pool-instance.
I do not understand he gives just 4 NTP’s and not 6 or 8, like 4x IPv4 and 2x IPv6 on all.
Systems that run in prio IPv6 will pick the IPv6 servers and if not there the IPv4’s.
I doubt he must change much code.
Just offer more pool servers
I should not matter for the load on them as Chrony (do not know about NTP) lowers the requests on other then the best server anyway by polling them less.
Minpoll / Maxpoll works good for that.
Finally, the latest Beta of the Fritzbox does let me do IPv6 properly with a firewall and a no nonsense approach.
I have added another server to the IPv6 pool.
ntp.heppen.be now servers 4xIPv4 and 3xIPv6
Adding to this, I am running three NTP servers and all of them are IPv6 enabled. Funny though, only two of them have IPv4 addresses.
I’m pro IPv6 and we need more zones to be v6 enabled. I’ll add one more server with IPv6 in India zone by next month.
Mine has IPv6 as well including AAAA record and reverse. IPv6 FTW!
Great to hear, but the real problem (or should I say, the remaining problem right now) is the missing AAAA-records in *.pool.ntp.org.
0.pool.ntp.org does not have one
1.pool.ntp.org does not have one
3.pool.ntp.org does not have one
Only 2.pool.ntp.org (and the variants, like 2.vendor.pool.ntp.org and 2.country.pool.ntp.org) have an AAAA.
That’s sad and I wish it would be fixed.