[GH-ISSUE #198] Suggestion to add an IPv6 resolver notice in FAQ #73

New issue

Closed

opened 2026-02-28 14:16:05 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 14:16:05 +03:00

Owner

Originally created by @catinello on GitHub (Sep 23, 2020).
Original GitHub issue: https://github.com/abh/ntppool/issues/198

I was looking for an IPv6 NTP server and the project clearly provides them. It is not obvious though and I couldn't find any info about it on the website. Only after a while of trying the DNS entries I found that all zones that contain a second (2.) entry have IPv6 addresses available.

Searching the web for a reason, lead me to an archived blog entry for world IPv6 day in 2011. It referenced the zone entries and that they would stay even after that day.

Would it be possible to mention this in the "How do I use ..." or an FAQ on the site? To address people that are looking for IPv6 servers. The numbers of constant 1000+ servers in the last 3 years are mentioned on the front page, but they are not used in the default DNS entries for whatever reasons. It probably also explains a lot of issues for IPv6 only environments that use the default addresses until #176 is solved.

Thank you.

Originally created by @catinello on GitHub (Sep 23, 2020). Original GitHub issue: https://github.com/abh/ntppool/issues/198 I was looking for an IPv6 NTP server and the project clearly provides them. It is not obvious though and I couldn't find any info about it on the website. Only after a while of trying the DNS entries I found that all zones that contain a second (2.) entry have IPv6 addresses available. Searching the web for a reason, lead me to an archived blog entry for world IPv6 day in 2011. It referenced the zone entries and that they would stay even after that day. Would it be possible to mention this in the "How do I use ..." or an FAQ on the site? To address people that are looking for IPv6 servers. The numbers of constant 1000+ servers in the last 3 years are mentioned on the front page, but they are not used in the default DNS entries for whatever reasons. It probably also explains a lot of issues for IPv6 only environments that use the default addresses until #176 is solved. Thank you.

kerem closed this issue

2026-02-28 14:16:05 +03:00

kerem commented

2026-02-28 14:16:06 +03:00

Author

Owner

@mdavids commented on GitHub (Oct 14, 2021):

Or, even better; add AAAA-records to the entire pool. We can already see folks choosing their own way, by configuring 2.pool.ntp.org (the only one providing AAAA-records) as their default server.

By default, Chrony on CentOS uses the 2.centos.pool.ntp.org as the time server. And for Android it’s the same thing. AVM (manufacturer of Fritz!Box CPE’s) also ships by default with 2.europe.pool.ntp.org.

These are undesired side effects and nothing less than nasty workarounds for an NTP pool which is lagging behind.

@mdavids commented on GitHub (Oct 14, 2021): Or, even better; add AAAA-records to the entire pool. We can already see folks choosing their own way, by configuring 2.pool.ntp.org (the only one providing AAAA-records) as their default server. By default, Chrony on CentOS uses the 2.centos.pool.ntp.org as the time server. And [for Android it’s the same thing](https://android.googlesource.com/platform/frameworks/base/+/40caf8f4432acd2b9d9230b2b1371660521415c2/core/res/res/values/config.xml#820). AVM (manufacturer of Fritz!Box CPE’s) also ships by default with 2.europe.pool.ntp.org. These are undesired side effects and nothing less than nasty workarounds for an NTP pool which is lagging behind.

kerem commented

2026-02-28 14:16:06 +03:00

Author

Owner

@catharsis71 commented on GitHub (Nov 12, 2022):

please please please add AAAA records to the main pool

@catharsis71 commented on GitHub (Nov 12, 2022): please please please add AAAA records to the main pool

kerem referenced this issue

2026-03-01 17:25:16 +03:00

[GH-ISSUE #73] Review/remove/replace <div class="block"> #325

kerem referenced this issue

2026-03-13 14:58:32 +03:00