Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion to add an IPv6 resolver notice in FAQ #198

Closed
catinello opened this issue Sep 23, 2020 · 2 comments · Fixed by #238
Closed

Suggestion to add an IPv6 resolver notice in FAQ #198

catinello opened this issue Sep 23, 2020 · 2 comments · Fixed by #238

Comments

@catinello
Copy link

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.

@mdavids
Copy link

mdavids commented 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.

@catharsis71
Copy link

please please please add AAAA records to the main pool

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants