Or you could switch to the OpenBSD OpenNTPd
I run it on Solaris and OS X (on a machine where the stock xntpd drifts uncontrollably by minutes a week), it's perfectly fine for most use-cases.
Get busy, sysadmins, there's a bunch of network time protocol (NTP) bugs to squash. The bugs were turned up in a code audit by Cisco's Talos business (which can surely feel the coals of hell being heaped upon its head for working in a Back to the Future joke in the bug-branding). Talos has been working on the code base of the …
I've found this on OSX as well. Macbooks that are separated from the network will often go minutes out of sync before they're re-connected a few hours later.
Interesting, is that because the OSX NTP implementation does not generate a drift file over time, or because the system clock is somehow unstable? Worth keeping an eye on.
Borked the whole network so fast you won't believe it. Whole damn network had to be rebuilt from scratch and the files restored from backup.
For whatever reason, the internet service we'd been using to get the NTP from NIST went down. So the server went down it's list of authoritative services which had of course been left on the defaults. Again for whatever reason, each level wasn't authoritative until it reached the very last one that it had to accept. That source: the date for the firmware for the core switch. As the date was circa 2004 and the firmware was circa 1992... Yeah, bad thing happened.