pool.ntp.org hardcoded which goes against ntp.org policy #376

New issue

Open

opened 2026-02-20 08:22:19 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 08:22:19 -05:00

Owner

Originally created by @julemand101 on GitHub (Jul 24, 2025).

Originally assigned to: @ym on GitHub.

Disclaimer

I have read and understood the disclaimer.

Application version

dev

System version

dev

Device model

None

Extension model

None

Remote device Hardware

No response

Remote device OS

No response

Bug description

I can see in ntp.go that the timeserver pool pool.ntp.org are being hard-coded:
github.com/jetkvm/kvm@55fbd6c359/internal/timesync/ntp.go (L19-L22)

This goes against the ntp.org's policy for vendors: https://www.ntppool.org/en/vendors.html

Which have following sections:

You must get approval from the server operator before you hardcode any IP addresses or hostnames. This is easy to get if your own organization runs the NTP servers you are planning to use. In most other cases you will not get it.

Do not use the standard pool.ntp.org names as a default configuration in your system. The NTP Pool can offer services for you, but it must be setup in advance (see below).

And:

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.

You can apply for a vendor zone here on the site.

If you have an open source ntpd implementation or an operating system including ntpd, we ask that you make a reference in the configuration file or documentation encouraging people to join the pool.

If you are a commercial / closed-source vendor we will ask for a small contribution to help scaling the pool to meet demands.

Questions? Email ask@develooper.com.

And:

Open source projects

Open Source projects are of course particularly welcome to use the pool in their default setup, but we ask that you get a vendor zone when using the pool as a default configuration.

Originally created by @julemand101 on GitHub (Jul 24, 2025). Originally assigned to: @ym on GitHub. ### Disclaimer - [x] I have read and understood the disclaimer. ### Application version dev ### System version dev ### Device model None ### Extension model None ### Remote device Hardware _No response_ ### Remote device OS _No response_ ### Bug description I can see in `ntp.go` that the timeserver pool `pool.ntp.org` are being hard-coded: https://github.com/jetkvm/kvm/blob/55fbd6c359f308b764bf1374a031370dd525aa66/internal/timesync/ntp.go#L19-L22 This goes against the ntp.org's policy for vendors: https://www.ntppool.org/en/vendors.html Which have following sections: > You must get approval from the server operator before you hardcode any IP addresses or hostnames. This is easy to get if your own organization runs the NTP servers you are planning to use. In most other cases you will not get it. > > Do not use the standard pool.ntp.org names as a default configuration in your system. The NTP Pool can offer services for you, but it must be setup in advance (see below). And: > **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. > > You can[ apply for a vendor zone](https://manage.ntppool.org/manage/vendor) here on the site. > > If you have an open source ntpd implementation or an operating system including ntpd, we ask that you make a reference in the configuration file or documentation encouraging people to [join the pool](https://www.ntppool.org/join.html). > > If you are a commercial / closed-source vendor we will ask for a [small contribution](https://www.ntppool.org/vendors/contribute.html) to help scaling the pool to meet demands. > > Questions? Email [ask@develooper.com](mailto:ask@develooper.com). And: > **Open source projects** > > Open Source projects are of course particularly welcome to use the pool in their default setup, but we ask that you [get a vendor zone](https://www.ntppool.org/en/vendors.html#vendor-zone) when using the pool as a default configuration.

deekerman added the

status: working-in-progress

component: timesync

labels

2026-02-20 08:22:19 -05:00

deekerman commented

2026-02-20 08:22:20 -05:00

Author

Owner

@IDisposable commented on GitHub (Aug 13, 2025):

Oh, sorry, that's on me... I'll follow up with the pool folks. Just as a slightly bit better, the PR https://github.com/jetkvm/kvm/pull/609/ at least (once merged) will use pool.ntp.org instead of those... and once the UI to configure those things is available (that PR honors the settings that will eventually be available), then it will be up to you.

@IDisposable commented on GitHub (Aug 13, 2025): Oh, sorry, that's on me... I'll follow up with the pool folks. Just as a slightly bit better, the PR https://github.com/jetkvm/kvm/pull/609/ at least (once merged) will use pool.ntp.org instead of those... and once the UI to configure those things is available (that PR honors the settings that will eventually be available), then it will be up to you.