NTP
NTP, the Network Time Protocol, is an important but often overlooked piece of infrastructure, despite Y2K making time-keeping a lot more relevant to the average network. Probably the foremost implementation of it is the NTP daemon series that David Mills is responsible for.
Mills's Ntpd
The 4.1.X[10] family of release versions of ntpd do not support NTP over IPv6. Version 4.1.74, which was a development snapshot of the code that became the 4.2.0 release of ntpd, was the first version to support IPv6. All releases after this (including 4.2.0) should support IPv6 if your operating system does.
Details of the most recent production, development snapshot and development versions of ntpd can be found at http://www.ntp.org/, including downloads of releases, snapshots and details of how to get development versions, if you need bleeding-edge features.
The network support in ntpd, as currently implemented, will only try to use the first address returned for any hostname. This has some serious implications for IPv6-capable ntpd—it will not fall back to IPv4 if an NTP server cannot be reached over IPv6. Indeed, ntpd will not fall back to other IPv4 addresses if the contacting server's first IPv4 address does not work out. This means that upgrading to a version of ntpd that can speak IPv6 may result in it losing contact with your NTP servers.
So, how can you avoid getting out of touch? One simple option is to tell ntpd to use only IPv4 by using the -4 command line option. Naturally, this isn't ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access