On Feb 25, 2017, at 11:15 AM, Max Grobecker <[email protected]> wrote:
> I just noticed that there are some NTP servers in the pool which are serving > in all regions > and which are obviously anycasted [1]. > For example this server, provided by NTT communications: > -> http://www.pool.ntp.org/scores/129.250.35.251 > > It's just 0.5 ms away from the LAX monitoring server and for me (near > Duesseldorf) about 5ms away located in Frankfurt. > That is pretty good to have an anycasted NTP server which is available to > nearly all networks with very low fault rates. My understanding is that anycast works fine for DNS, but breaks the NTP protocol. With NTP, you’re supposed to have one and only one system clock per IP address. Otherwise, you break critical underlying assumptions. For the same reason, you can’t put multiple NTP servers behind a load balancing switch. Is this not correct? Did I miss something? -- Brad Knowles <[email protected]>
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
