[email protected] said: > 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.
Actually, I think it should be pool.XYZ.com or pool.ntp.XYZ.com rather than XYZ.pool.ntp.org That lets the vendor/ISP recover in case the pool goes out of business. It also offers a way out for the pool in case their DNS code is buggy. If the pool agrees (which I expect it would), that can redirect to pool.ntp.org or one of the geographic/country names if the ISP is in one country/region. If they are installed by an ISP, XYZ should probably be the ISP rather than the manufacturer. -- These are my opinions, not necessarily my employer's. I hate spam. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
