In my view, it would be good for ntpd to keep track of the hostname
originally used to configure the association and (at least by default)
use leftover alternate addresses or re-resolve the name after the
association becomes unreachable. That would involve rejecting
duplicate associations with the same hostname in addition to the
current duplicate remote address rejection. It would also mean less
predictable behavior, as ntpd would begin using more than the first
address returned by DNS for unicast associations by name. Setups
involving "restrict" by numeric address which work today could develop
problems not previously seen. Name-based restrictions in recent ntpd
are applied to all addresses returned (in 4.2.6 as well, I believe,
but not 4.2.4). I doubt this will be tackled before the next
ntp-stable, whether it's called 4.2.8 or 4.3.0.
Cheers,
Dave Hart
Yes, that approach (remembering the original name) sounds sensible to me,
although I can see there are problems with it as well. Thanks for the
information.
Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: [email protected]
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
