True about the part where a vendor would be able to recover, but that would leave the pool admins with lesser control on their end (e.g., DNS-fuckups). I guess it would doable though, if pool.XYZ.com where to become a CNAME to XYZ.pool.ntp.org, then people get to keep control on both ends.
Though on the other hand, with the current vendor's average behavior and interest in NTP, I don't really think vendors care to keep control. Putting in any other third party NTP (other than the pool or their own) doesn't leave them them any control either, does it? It's not like they've ever seem to have wanted to keep control, or have asked for it. Also, it could be confusing (e.g. to end-users) about affiliations. Or branding-issues. There's probably more to it than meet's the eye. - Roelant. On Tue, Nov 24, 2009 at 6:21 AM, Hal Murray <[email protected]> wrote: > 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. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
