> I would also welcome any inputs on where improvements are needed in order to > make the pool completely IPv6-ready. The current situation where > 2.pool.ntp.org returns IPv6 addresses was a good step four years ago. However > with respect to the growth of the IPv6 adoption rate, IPv6 support is IMO > already mandatory for any large-scale internet service. The longer we wait, > the less predictible the transition process will be. I'm very interested if I > can be of any help.
My 2 cents: AAAA records may be added for each [0-3].ANY.pool.ntp.org name. It needs some documentation update only. Users should be informed that IPv4 connection can be forced when necessary with "server -4 FQDN" configuration. Gabor _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
