On 12/02/2014, at 12:53 pm, Ben
On Wed, Feb 12, 2014 at 12:49:39PM +1300, Don Stokes wrote:
It might also be a useful occasion to plug nz.pool.ntp.org. If you have Right after major attacks on open NTP servers doesn't seems like the best time to plug opening your NTP servers ... 8-)
Seriously though, NTP is a service ISPs should be providing to customers. Doing local anycast of NTP service to well-run stratum 2 servers, (in turn talking to well-run stratum 1 servers, such as the NZRS ntp.net.nz servers and the MSL servers) is a far better idea than having punters querying random NTP pools of unknown quality, or opening up NTP servers to the whole world.
I think the biggest problem with this idea is that it's recommended to have at least 3 NTP servers. So not only do you have to encourage ISP's to have a NTP server, but multiple NTP servers..
At least 3 - you need 3 to NTP to do its job and eliminate bad tickers. If you only have 2, you end up with an average between them, even if one is an hour out. For resiliency (so that one can be offline or unreachable for an extended period, and lets face it, this is the Internet) you need 4. Others disagree and consider a bad ticker to be a fault that should be resolved just like poor connectivity, and only engineer for one of these situations at a time. You can choose :-) -- Nathan Ward