Does `fedora.pool.ntp.org` support IPv6?

Ask Fedora
,
1

What prompted me to ask is the undermentioned:

2

As I understand it, fedora.pool.ntp.org is a vendor zone not under our control, it exists to the NTP pool can better distribute load on servers (see their FAQ). At any rate, for me both 2.fedora.pool.ntp.org and 2.pool.ntp.org resolve to both A and AAAA records, while 0.*, 1.* and 3.* and the subdomain itself don’t.

1 Like
3

I see IPv6 time sources being used by cronyd.
That is configured with pool 2.fedora.pool.ntp.org iburst
Here are the sources I’m seeing:

$ chronyc -n sources
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ 2a05:d01c:9d2:d200::be00:4    2  10   377   914   -161us[ -259us] +/- 6328us
^+ 178.62.68.79                  2  10   377    58   -465us[ -465us] +/- 8323us
^* 2001:8b0:1827:ef43::14:1      1  10   377    71    -83us[ -190us] +/- 6126us
^+ 2a03:b0c0:1:d0::1f9:f001      2  10   377    31   -750us[ -750us] +/- 8950us
1 Like
4

@nphilipp and @barryascott, thanks for the confirmation! In that case, I surmise that using 2.fedora.pool.ntp.org is the correct thing to do to ensure that their vendor telemetry isn’t reduced whilst ensuring that I always have IPv6 support.

1 Like