[ resending from an account that doesn’t have -all in it’s spf record ]
> On Jul 21, 2019, at 14:51, Hal Murray <[email protected]> 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 Hi Hal, There isn’t currently. It wouldn’t be terribly hard to add, but it’s not super clear to me that it’s the appropriate solution (or maybe even exactly what the problem is!). > 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. For users using the “pool” keyword, I think it’d make sense to every ~24 hours (?) replace the worst performing server and, for example, every week (?) replace the “oldest” server. The reason to replace the oldest server (if it’s still in the pool or not) would be to continuously load balance between all the available servers, rather than have clients hold on to servers that then get a slowly increasing load. If “pool” configured clients were the majority and they just had a policy of always (slowly) rotating servers, this shouldn’t happen. > That won't catch the case where the pool DNS name is used as a server. If we > put a simple still-there check in the server case, clients would end up > switching servers every time they checked. I don't see any harm in that. I don’t think I understood what this meant. Ask _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
