They probably would not be happy about millions of clients. I assumed this was for a particular situation with a poorly behaving client.Shoudnt most welbehaving clients change to a different pool server if it does not answer and if it answes with incorrect time it should disregard the reply?
Br, Thomas On Mon, Jul 22, 2019 at 9:27 AM Miroslav Lichvar <[email protected]> wrote: > On Mon, Jul 22, 2019 at 12:05:41AM +0200, Thomas Hedberg wrote: > > Hi Hal > > > > What about a http lookup using curl or something similar at > > https://www.ntppool.org/scores/X.X.X.X/log?limit=1&monitor=* ? > > > > It will give you the current score of the IP and probably an error if the > > IP is not in the pool anymore. > > That might work, but I'm not sure if the admins would be happy with > millions of clients periodically making HTTP requests to their > servers. Something with DNS might be cheaper, but probably still a > significant burden on the resources. > > When a server is removed from the pool, I think the best thing to do > is to stop responding. Most clients will switch to another pool server > within few polling intervals. The rest will not bother to check a URL > or special DNS name to see if the server is still in the pool. > > -- > Miroslav Lichvar > _______________________________________________ > pool mailing list > [email protected] > http://lists.ntp.org/listinfo/pool > _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
