M Graff wrote: > Seriously, if ntpd doesn't try both IPv6 and IPv4 addresses for a given > host then it would seem to be broken.
Hosts not responding is a normal state for ntp. Since it never retries dns lookups beyond the first boot - it simply stores ip addresses - it's not practical to implement the same way web clients do. You could make ntp retry dns lookups occasionally... this would be good for the pool too. First you've got to get it past the ntp devs, then you've got to get it implemented in all the 3rd party ntp implementations - including microsoft. Or you can go the simple route of giving it its own namespace and have an ipv6 pool (albeit experimental for now) next week/month rather than in 2-3 years time. Tony _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
