On Tue, Dec 27, 2011 at 03:39, Danny Mayer <[email protected]> wrote: > You can use round robin dns for NTP. There's nothing wrong with that. > It's load balancing that must NOT be used as you would get different > answers from different systems each time.
Danny is right here, though there's an exception implied by his explanation: If your load balancing solution is mapping the same address/port pairs to the same backend server for the most part, you can use it for NTP service with less negative impact, vs. load balancing each request to a potentially different backend server. The key point is ntpd assumes each remote address represents a single oscillator. State is kept by ntpd clients for each association, especially the clock filter register, so that unpredictable load balancing will foul time transfer. Cheers, Dave Hart _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
