Stop using pool.ntp.org by default

[willglynn]

Talos currently hardcodes pool.ntp.org as a default time server. The NTP Pool for vendors page expressly forbids operating system vendors from doing this:

Audience for this document

Anyone distributing an appliance, operating system or some other kind of software using NTP.

• Appliance vendors (Netgear, D-Link, Linksys, ...)
• Operating System vendors (Debian, RedHat, FreeBSD, m0n0wall, ...)
• Software vendors

…

Get your vendor zone

To allow you to use the pool as the default time service in your application, we will set you up with special hostnames, for example 0.vendor.pool.ntp.org, 1.vendor.pool.ntp.org, 2.vendor.pool.ntp.org and 3.vendor.pool.ntp.org.

You must absolutely not use the default pool.ntp.org zone names as the default configuration in your application or appliance.

The constant is aware of this requirement:

https://github.com/siderolabs/talos/blob/a009f5c60c9506dd5064106bbef38fe36813db64/pkg/machinery/constants/constants.go#L701-L705

The comment dates to early 2019. I'm not sure what naming needed sorting, but I imagine it's been resolved in the interim.

[smira]

we tried multiple times to apply, but never had a response back, happy to make a change if you have a way to push that request through

[willglynn]

Hmm… I tried filling out the form, and it says it's already in use:

Querying 0.talos.pool.ntp.org IN A returns NXDOMAIN, so it's already in use but it doesn't exist.

I'll send an email. The vendors@ link goes to ask@, so I'll address both.

[onedr0p]

Since talos is taken could you all apply for a sidero pool name?

[steverfrancis]

The "Talos" zone is taken by us - we applied for it well over a year ago, and our application has been stuck in "pending" since, despite repeated emails