On 11/23/2009 09:14 AM, Shoppa, Tim wrote:
I think that because of the way the load will be distributed across time
and space, that the
vast majority of vendors who use well-behaved NTP clients should be
allowed as part of
the rules of engagement to use pool.ntp.org without even asking.
It’s the boneheaded clients that request at the top of every hour, or
that start
Launching requests at insane rates on certain return codes, that are the
problem children.
These still exist but aren’t quite as bad as a few years ago IME.
That's all well and good, but how do know that Vendor XYZ is going to
"behave". I think if a vendor wants to deploy a large amount of NTP
devices they should have their own XYZ.pool.ntp.org dns entry. That
gives the vendor, and us more control of how and where those packets go.
Also, it's trivial to setup. Not to speak for ASK, but setting up a DNS
entry should take about 15 minutes.
- Scott
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
