Skip to content

Getting started

Ntpd-rs is an implementation of the NTP protocol. It aims to synchronize your system's clock to time received from the internet. It can also, when configured as server, provide time to other machines on the network.

Installation

Installation instructions for your system can be found in the installation guide. For first time users, we strongly recommend using either your OS package repository packages, or the packages we provide. If you have installed ntpd-rs from source, and you have installed files in different locations than the default, you may need to modify the instructions below.

Checking the synchronization.

The default configuration for ntpd-rs sets it up to synchronize with four servers chosen from the NTP pool. We can check its synchronization status using:

ntp-ctl status

If everything is installed and working correctly this will display information looking like:

Synchronization status:
Dispersion: 0.000104s, Delay: 0.005740s
Desired poll interval: 16s
Stratum: 3

Sources:
ntpd-rs.pool.ntp.org:123/20.101.57.9:123 (1): -0.022944±0.000218(±0.004720)s
    poll interval: 16s, missing polls: 0
    root dispersion: 0.103531s, root delay:0.001434s
ntpd-rs.pool.ntp.org:123/35.204.193.221:123 (2): +0.000564±0.000138(±0.007323)s
    poll interval: 16s, missing polls: 0
    root dispersion: 0.000000s, root delay:0.007538s
ntpd-rs.pool.ntp.org:123/94.198.159.15:123 (3): +0.000140±0.000202(±0.005725)s
    poll interval: 16s, missing polls: 0
    root dispersion: 0.000015s, root delay:0.000015s
ntpd-rs.pool.ntp.org:123/95.211.123.72:123 (4): +0.000052±0.000189(±0.005118)s
    poll interval: 16s, missing polls: 0
    root dispersion: 0.039536s, root delay:0.021667s

Servers:

The first section gives some general information on the time synchronization. The dispersion is a measure for how precise it thinks the local time is, and the delay is a measure of how long the communication delay to the best (most precise) server is. Desired poll interval indicates how often it currently wants to know the time from downstream servers, and stratum indicates how many servers are between us and a reference source of time such as an atomic clock or GPS receiver. Stratum will always be at least 2 when configured as a client using only sources from across the internet.

Next, we get information on each of the time sources, showing the measured offset and the uncertainty on that, as well as (between brackets) the delay to the server. We also show the poll interval used for that particular source. This can be different from the desired poll interval if a server requests us to do fewer queries. Finally, missing polls gives an indication of how many times we have tried to poll the server since last getting a time measurement for it.

The final section is empty, but if we were running a server, it would show statistics on how often the server is used.

Configuring a custom time source

The sources ntpd-rs uses to get the current time can be configured in the /etc/ntpd-rs/ntp.toml configuration file. Suppose that, in addition to the sources from the NTP pool, we also always want to use two sources from the time.nl pool. To do this, we add the following lines to the configuration file:

[[source]]
mode = "pool"
address = "ntp.time.nl"
count = 2

After restarting the daemon (using sudo systemctl restart ntpd-rs if you are using Linux) and waiting a bit for it to synchronize, the status now looks like

Synchronization status:
Dispersion: 0.000123s, Delay: 0.005496s
Desired poll interval: 16s
Stratum: 2

Sources:
ntp.time.nl:123/94.198.159.10:123 (1): +0.000380±0.000249(±0.005496)s
    poll interval: 16s, missing polls: 0
    root dispersion: 0.000122s, root delay:0.000000s
ntp.time.nl:123/94.198.159.14:123 (2): -0.000046±0.000154(±0.005520)s
    poll interval: 16s, missing polls: 0
    root dispersion: 0.000122s, root delay:0.000000s
ntpd-rs.pool.ntp.org:123/84.245.9.254:123 (3): -0.000288±0.000698(±0.008572)s
    poll interval: 16s, missing polls: 0
    root dispersion: 0.000305s, root delay:0.006226s
ntpd-rs.pool.ntp.org:123/83.98.155.30:123 (4): +0.000000±0.000163(±0.005186)s
    poll interval: 16s, missing polls: 0
    root dispersion: 0.005020s, root delay:0.004898s
ntpd-rs.pool.ntp.org:123/162.159.200.123:123 (5): -0.000380±0.000140(±0.004535)s
    poll interval: 16s, missing polls: 0
    root dispersion: 0.000259s, root delay:0.003662s
ntpd-rs.pool.ntp.org:123/5.255.99.180:123 (6): +0.000193±0.000203(±0.005414)s
    poll interval: 16s, missing polls: 0
    root dispersion: 0.008499s, root delay:0.005661s

Servers:
where we see the two servers from time.nl added to the list of sources.

Where to go from here

You now have a working NTP client, can check its status, and if desired modify the sources it uses for time. There are multiple directions to go from here.

If you want more certainty around the authenticity of your time sources, you can take a look at using NTS.

Setting up your own time server is explained in our server setup guide.

When operating ntpd-rs as part of a larger critical system, you may also be interested in our guidance on hardening ntpd-rs.