[ntp:questions] Badly drifting system time

Wolfgang S. Rupprecht wolfgang+gnus20061203T101934 at dailyplanet.dontspam.wsrcc.com
Sun Dec 3 18:33:57 UTC 2006


yorhel at gmail.com writes:
> server 0.nl.pool.ntp.org
> server 1.nl.pool.ntp.org
> server 2.nl.pool.ntp.org
>
> restrict 0.nl.pool.ntp.org noquery nomodify
> restrict 1.nl.pool.ntp.org noquery nomodify
> restrict 2.nl.pool.ntp.org noquery nomodify

    $ host  0.nl.pool.ntp.org
    0.nl.pool.ntp.org has address 32.112.56.88
    0.nl.pool.ntp.org has address 62.166.22.106
    0.nl.pool.ntp.org has address 80.85.129.25
    0.nl.pool.ntp.org has address 81.68.241.179
    0.nl.pool.ntp.org has address 88.159.80.12
    0.nl.pool.ntp.org has address 131.211.84.189
    0.nl.pool.ntp.org has address 194.88.2.60
    0.nl.pool.ntp.org has address 194.165.35.111
    0.nl.pool.ntp.org has address 213.84.230.57

Does the above restriction now work?  At one point restrict lines with
multihomed or round-robin hosts would cause the restriction to only be
applied to one of those addresses.  It is always possible to have one
address selected for the "server" line and a different address to be
selected for the "restrict" line.

For pools.ntp.org and other round-robin hosts, it is probably safest
to just to use a default restriction that allows any address to tell
you the time.  This is what I have used in the past:

    restrict default nomodify notrap nopeer
    restrict ::      nomodify notrap nopeer

-wolfgang
-- 
Wolfgang S. Rupprecht                http://www.wsrcc.com/wolfgang/




More information about the questions mailing list