Your NTP configuration is wrong

[Gerald Combs]

This is a good strategy, since a nearby stratum [234] server will almost
always be better than a faraway stratum 1 server.  My "ntp.conf"s are
typically

server <nearest box "traceroute www.google.com" + "ntpdate -q" finds>
server us.pool.ntp.org
server us.pool.ntp.org

The first "server" entry usually ends up being the first upstream router
on the provider's side of whatever connection I'm on.  So far it's
worked well.

BTW, I forgot to mention that the OpenBSD/OpenSSH folks have recently
come out with their own NTP daemon:  http://www.openntpd.org/

david nicol wrote:
> A lot of routers are NTP servers.  `traceroute` gives IP addresses of
> routers.  Ignore ones that have the time wrong.
> 
> On Sun, 2004-08-01 at 19:49, Gerald Combs wrote:
> 
>>I ran across this project recently.  It's a clever solution to a problem
>>that hasn't received much attention (overloaded public NTP servers).
>>Apparently it's been around a while:
>>
>>    http://www.pool.ntp.org/