Evandro Menezes wrote: > Many former participants of the NTP pool have stated that they > continue with lingering NTP clients after they left the pool. > > The reason for this is that ntpd never tries to resolve an IP address > (assuming that *.pool.ntp.org was used) ever again. Therefore, > clients which are seldom rebooted, will stick to the same NTP servers > for a long time. > > I was wondering if it would make sense to open some windows when ntpd > could resolve the addresses again. One such window would be when ntpd > steps the time, which puts it into a state perhaps similar to when > it's started. > > I imagine that such a new resolution of addresses for the NTP servers > in the pool would also help distributing the load among them more > fairly. > > Thoughts?
This is the next item on my worklist but requires a lot of work. See http://support.ntp.org/bin/view/Dev/DNSServerFailover for details. Deciding when to do a new lookup is the biggest question so that needs to be configuration options. Note that sntp clients may never do a new lookup if they just continue to run and no implementation that I know of supports this today so there won't be immediate relief for the pool even when implemented. Danny Danny _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
