Enable IPv6 for OpenWRT's time servers (ntp)

I just noticed, that time and date is not updated on nodes in my IPv6-only network.

Out of 0–3, only 2.openwrt.pool.ntp.org has AAAA records enabled. If those servers are maintained by members of the OpenWRT project, I would be happy if they could enable IPv6 for all of them.

2.openwrt.pool.ntp.org.	81	IN	AAAA	2a01:4f8:110:12d5::2
2.openwrt.pool.ntp.org.	81	IN	AAAA	2a01:4f8:c2c:3d20::1
2.openwrt.pool.ntp.org.	81	IN	AAAA	2a01:238:427e:1e00:f21d:ee49:2a64:3256
2.openwrt.pool.ntp.org.	81	IN	AAAA	2a01:4f8:200:3296::2
1 Like

They're not - they'remaintained just as any other server in the pool:

See: https://www.pool.ntp.org/en/vendors.html#vendor-zone

I would suggest using IPv6 IP or a server with a known AAAA record.

2 Likes

That is a documented decision by ntp.org, only the '2.*.ntp.org' servers are IPv6 enabled (sorry, can't find my reference right now, but I too want all my ntp servers to be IPv6 capable, and I've dug into this).

Here's a list of v6 capable servers I've collected over the years. I occasionally ping them to get the ones with lowest RTT, then use the four that are 'closest' to me in that regard. Those Hurricane Electric (he.net) ones in San Jose and Fremont California are always very fast for me, but that's because of geographic proximity. Cloudflare and Google are almost always good, too.

    2.pool.ntp.org
    2.us.pool.ntp.org
    clock.fmt.he.net
    clock.sjc.he.net
    ntp.he.net
    time-d-wwv.nist.gov
    time-e-wwv.nist.gov
    time.cloudflare.com
    time.google.com
3 Likes

Here’s an old reference:

2 Likes