🖥️ Client Setup — Linux & Windows

ntp1.prichindel.com (89.28.74.161, live monitoring score) is a genuine Stratum 1 server, disciplined directly by GPS and hardware PPS. Below is how to point the common Linux and Windows time clients at it, and what each option actually buys you.

Linux — chrony (recommended, most modern distros)

Add a line to /etc/chrony/chrony.conf (or drop a file in /etc/chrony/conf.d/):

server ntp1.prichindel.com iburst

Then restart and check it locked on:

sudo systemctl restart chrony
chronyc sources
chronyc tracking
Outcome: iburst sends a fast burst of requests on startup instead of waiting for the normal poll interval, so chrony locks on within seconds rather than minutes. Keep your existing pool servers alongside this line rather than replacing them — chrony needs at least a few sources to detect a server quietly drifting wrong (a "falseticker") instead of trusting whichever one you have configured. One good Stratum 1 plus a couple of pool servers is a better setup than one server alone, however good it is.

Linux — systemd-timesyncd (lighter, less precise)

Edit /etc/systemd/timesyncd.conf:

[Time]
NTP=ntp1.prichindel.com
FallbackNTP=pool.ntp.org
sudo systemctl restart systemd-timesyncd
timedatectl timesync-status
Outcome: timesyncd is SNTP-only — it slews the clock but doesn't do chrony's statistical filtering or falseticker detection, and polls far less aggressively. Fine for a desktop or a container; if you care about accuracy to the millisecond, use chrony instead.

Windows — built-in Internet Time (easy, coarse)

Settings → Date & Time → Additional clock settings → Internet Time → Change settings → Server:

ntp1.prichindel.com
Outcome: Windows' default w32time client syncs roughly once an hour and is built for "close enough" desktop clock-setting, typically within a second or so. It will use the server, but it won't get you anywhere near what the server itself is capable of.

Windows — w32time, tuned for accuracy (PowerShell / admin cmd)

w32tm /config /manualpeerlist:"ntp1.prichindel.com,0x8" /syncfromflags:manual /reliable:YES /update
net stop w32time
net start w32time
w32tm /resync /force
w32tm /query /status
Outcome: the 0x8 flag tells Windows to use full NTP client mode instead of the cruder SNTP fallback, and /reliable:YES lets a workstation treat this as an authoritative local source. You can shorten the polling interval further with reg add HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient /v SpecialPollInterval /t REG_DWORD /d 120 /f (polls every 2 minutes instead of the ~hour default) if you need tighter, more current sync — at the cost of a bit more traffic to the server.

Getting the most out of Stratum 1 timestamping

A Stratum 1 source is only as useful as the weakest link between it and your application. A few things actually move the needle:

  • Use chrony, not timesyncd or default w32time, if your application cares about sub-second accuracy — the simpler clients just don't poll or filter aggressively enough.
  • Keep more than one server configured. Stratum 1 accuracy from ntp1 doesn't help if a single misbehaving source can pull your clock without a second opinion to catch it.
  • Expect network jitter to be the real limit, not the server. ntp1 disciplines its own clock to sub-microsecond precision via GPS+PPS, but a typical client over the internet will see accuracy dominated by round-trip jitter on its own connection — realistically low single-digit milliseconds for most WAN clients, tighter for LAN/regional clients with a clean path.
  • Don't expect PPS-grade precision remotely. The hardware PPS signal disciplines the server's own clock; it isn't something a network client can receive over NTP. If you need PPS-grade timestamping yourself, you need your own GPS+PPS receiver — ntp1 can still be a useful independent cross-check for it.
  • NTS is not yet available here — queries are plain, unauthenticated NTP. Don't rely on this (or most public NTP servers) for a security-sensitive timestamp; use it for accurate time, not proof of origin.