On Fri, 26 Jan 2007, David Rawling wrote:
> I love the idea of a more friendly client - but perhaps the patch could be as
> simple as doing a new name lookup if the current server is not responding?
>
> So for example a client has configured:
>
> server 0.pool.ntp.org
> server 1.pool.ntp.org
> server 2.pool.ntp.org
>
> The machine he or she resolved from the name "1.pool.ntp.org" disappears for
> more than {arbitrary long time period - eg 24h}. Now resolve 1.pool.ntp.org
> to a new IP address and sync to it instead.
>
> I can imagine that there are huge benefits in terms of time stability to
> keeping the same servers active if they are responding with accurate time.
>
> Dave.
I think this would work just fine as a pool specific solution.
Now, we may ask ourselves, what if ntpd could be made better and at the
same time not only solve our pool problems, but indeed solve all useless
traffic linked with down ntp servers ?
It is a less selfish (from the pool server admin point of vue) solution
that would globally solve the problems linked with down servers.
You could configure ntpd once and forget it for a few years... ;-))
example :
main servers :
10.0.0.1
10.0.0.2
10.0.0.3
spare servers :
10.0.0.4
10.0.0.5
10.0.0.6
10.0.0.7
10.0.0.8
10.0.0.9
10.0.0.10
10.0.0.11
10.0.0.12
10.0.0.13
10.0.0.14
10.0.0.15
For the pool it could be :
main servers :
0.ca.pool.ntp.org
1.ca.pool.ntp.org
2.ca.pool.ntp.org
spare servers :
0.north-america.pool.ntp.org
1.north-america.pool.ntp.org
2.north-america.pool.ntp.org
0.uk.pool.ntp.org
1.uk.pool.ntp.org
2.uk.pool.ntp.org
0.pool.ntp.org
1.pool.ntp.org
2.pool.ntp.org
The ntp pool admin could also add more subzones so we could have :
main servers :
0.ca.pool.ntp.org
1.ca.pool.ntp.org
2.ca.pool.ntp.org
spare servers :
4.ca.pool.ntp.org
5.ca.pool.ntp.org
6.ca.pool.ntp.org
7.ca.pool.ntp.org
8.ca.pool.ntp.org
9.ca.pool.ntp.org
In the end, is it worthed to make ntpd better or do we just want to
fix our pool problems only?
This model is similar to having a lot of DNS root servers configured in
named db-cache file. Once every five or 10 year or so, you need to update
your config file because it does occur that servers change IPs.
Of course, one may want to update it more often due to security concerns
but that is another story.
see: http://www.internic.net/zones/named.root
-Louis
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
