Skip to content
AdminKit

NTP (Network Time Protocol)

What is NTP (Network Time Protocol)?

NTP (Network Time Protocol), defined in RFC 5905, synchronizes a device's clock against a hierarchy of time servers -- accuracy that DNSSEC quietly depends on, since RRSIG signatures expire on a wall-clock timestamp. AdminKit's glossary covers RRSIG, the DNSSEC record an inaccurate NTP clock can break.

By AdminKit team, Netbase JSC · Updated

NTP (Network Time Protocol) is a protocol, defined in RFC 5905, for synchronizing a device’s clock against time servers arranged in a hierarchy of strata — IANA’s NTP Parameters registry, maintained alongside the RFC, catalogues the reference identifier codes (such as GPS or a specific radio station) a stratum 1 server reports for its clock source — stratum 0 reference clocks, stratum 1 servers attached to them, and successive strata synchronizing from the stratum above. The NIST Internet Time Service is one public example near the top of that hierarchy: NIST operates several stratum-1 network time servers. Most operating systems run an NTP client by default, quietly correcting clock drift in the background, which is why accuracy rarely gets a second thought until it’s wrong — Microsoft’s own Windows Time Service documentation describes exactly this kind of always-on background synchronization for Windows. It matters beyond simply showing the right time: DNSSEC’s RRSIG records, defined alongside the rest of DNSSEC in RFC 4034, carry explicit inception and expiration timestamps, and a device whose clock has drifted far enough can reject a valid signature as expired, or accept one that has genuinely expired, purely because its own idea of the current time is wrong. TLS certificate validity checks rest on the same assumption — an X.509 certificate’s validity window, and a time-stamped OCSP stapling response confirming it hasn’t been revoked, both depend on the same accurate clock, so an inaccurate one undermines a check like AdminKit’s TLS/SSL check that has nothing else wrong with it.

NTP (Network Time Protocol) is part of AdminKit’s machine protocols cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

How is NTP's time hierarchy organized?

In strata -- stratum 0 reference clocks, stratum 1 servers directly attached to them, and successive strata synchronizing from the stratum above, so most devices sync from a server several hops removed from the actual reference clock.

Why does an inaccurate clock break DNSSEC validation?

DNSSEC's RRSIG records carry explicit inception and expiration timestamps, and a device whose clock has drifted far enough can reject a valid signature as expired, or accept one that has genuinely expired, purely because its own idea of the current time is wrong.

Does clock drift only affect DNSSEC?

No -- TLS certificate validity checks rest on the same assumption; an inaccurate clock can undermine a certificate check, like AdminKit's TLS/SSL check, that has nothing else actually wrong with it.

Do most devices need to configure NTP manually?

Usually not -- most operating systems run an NTP client by default, quietly correcting clock drift in the background, which is why its accuracy rarely gets a second thought until something downstream, like a signature check, starts failing.