I do agree with Rob, that the users should re-resolve the pooladdresses once a day. I can even live with with once every week.
Another thing: I have loads of traffic on port 37 trying to reach my NTP server. I estimate that about 50% of the "NTP related traffic" goes to port 37 UDP. It would be very nice if there is a strong requirement not to use the pool for port 37 requests Met vriendelijke groet, Best regards, Thom van der Boon E-Mail: [email protected] ===== Thom.H. van der Boon b.v. Transito 4 6909 DA Babberich Tel.: [ tel:+31884272727 | +31 (0)88 4272727 ] Fax: +31 (0)88 4272789 Home Page: http://www.vdb.nl/ Van: "Rob Janssen" <[email protected]> Aan: [email protected] Verzonden: Dinsdag 23 juli 2019 10:38:15 Onderwerp: Re: [Pool] Server still in the pool? I am currently trying to get a server out of the pool before it gets decomissioned completely. It has been removed from the pool like two months ago, but it still receives a lot of requests. I have sent KoD on these requests for some time, but they keep coming in. I think most of them are from ISP routers that have pool.ntp.org as their default NTP server setting and query the pool in SNTP manner to set the router clock. Queries are usually either once per hour or once per day, but there is a huge amount of such routers. I think it should be put as a requirement on manufacturers of such routers that the re-resolve the DNS name at least once a day, instead of resolving it only once at bootup and then using the same IP address forever. But also there are more NTP-like users. They have a polling interval around 1024 seconds. They apparently are stabilized instances of ntpd or similar, but still a lot of them keep coming back when receiving KoD. Maybe the processing of KoD has been removed from ntpd just like the generation of it? As long as we cannot get such simple measures correctly implemented, forget about more complicated things. Sure you could add a lookup feature, but nobody is going to use it. Rob On 7/21/19 11:51 PM, Hal Murray wrote: > Is there any way for client code to determine if an IP Address is still in > the > pool? Maybe something like a DNS lookup on d.c.b.a.pool.ntp.org > > If there was a way to do that, it would be easy to update servers to check > occasionally and stop using servers that have left the pool. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
