From: Guillaume Le Vaillant <glv@posteo.net>
To: Leo Famulari <leo@famulari.name>
Cc: 71462@debbugs.gnu.org
Subject: bug#71462: Default ntp service configuration not working on IPv6 network
Date: Tue, 18 Jun 2024 08:21:51 +0000 [thread overview]
Message-ID: <8734pay82o.fsf@kitej> (raw)
In-Reply-To: <ZnDEPLI2vC9ssbwI@jasmine.lan> (Leo Famulari's message of "Mon, 17 Jun 2024 19:18:20 -0400")
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
Leo Famulari <leo@famulari.name> skribis:
> On Mon, Jun 10, 2024 at 08:30:32AM +0000, Guillaume Le Vaillant wrote:
>> On an IPv6-only network, the default configuration for ntp-service-type
>> doesn't work, because the default pool used (<0.guix.pool.ntp.org>)
>> doesn't have IPv6 addresses.
>>
>> In fact, the <1.guix.pool.ntp.org> and <3.guix.pool.ntp.org> pools don't
>> have IPv6 addresses either. Only the <2.guix.pool.ntp.org> pool works
>> with IPv6.
>>
>> Would it be possible to add IPv6 support to pools 0, 1 and 3?
>
> It's not something that we, as Guix, can do.
>
> The NTP pool is run by a separate organization, and the question of
> which DNS names should return AAAA (IPv6) records is open:
>
> https://community.ntppool.org/t/the-time-has-come-we-must-enable-ipv6-entirely/1968
>
> However, the reason they give us 4 different addresses is so that we can
> spread the load around. Our NTP services should choose randomly at
> run-time. Or we could just make number 2 the default, and then we'll
> have IPv6 support. Or something more complicated...
Thanks for the info. I'm now using pool 2 as the default on my IPv6-only
machines, and it works well.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2024-06-18 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 8:30 bug#71462: Default ntp service configuration not working on IPv6 network Guillaume Le Vaillant
2024-06-17 23:18 ` Leo Famulari
2024-06-18 8:21 ` Guillaume Le Vaillant [this message]
2024-10-19 12:51 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8734pay82o.fsf@kitej \
--to=glv@posteo.net \
--cc=71462@debbugs.gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.