Anthony DeRobertis wrote: > On Wed, Aug 08, 2007 at 09:52:21AM -0700, Chuck Swiger wrote: > >> If a very large organization like TT caches the result and fails to >> rotate the IPs in round-robin fashion, then any clients using those >> TT nameservers are going to hammer the IP which was first in the >> result from the pool.ntp.org nameservers. > > Hmmm, a very evil "solution" of making sure that the first result record > given to said organizations is always something silly, say 127.0.0.1 or > 169.254.0.1, comes to mind. > > /me wonders what the effects would be of doing it in general. Probably > wouldn't break ntpd too badly if you have working round robin because > you've got a 74% chance of not even seeing the silly value, and a much > higher chance of getting at least 3 working servers. > > </evil> > That's just hurting the end users - someone with an el cheapo router in turkey would suddenly get no time service (because typically they're only configured to get a single IP address). Wouldn't affect the ISP at all.
Ultimately we need to deal with it not only by getting TTNet to sort out their own NTP service but sorting out the pool so it can mitigate the spikes somehow. There are lots of ISPs out there who haven't yet used the pool - only takes one of the larger ones to do it and we're back to square one if we haven't sorted our end out. Tony _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
