> >The second part is where we're currently doing it by more or less abusing > >DNS. DNS is a mapping from names to numerical addresses, but it was never > >designed for the kind of load-balancing we're doing here. What we do > >works, kind of, but IMHO it's worth keeping in mind that tweaking DNS is a > >kludge I've started because I am too lazy to design a proper solution, > >which would be integrating support for server pools into ntpd directly. > > One might be able to improve this by having "pool.ntp.org" and other > relatively full domains (Europe, NA) be CNAMES which point to > 0.pool.ntp.org, 1.pool.ntp.org, and so forth, which would let you spread > the load-balancing between 30+ boxes rather than just 10...? >
I don't think that would work. You can't have a CNAME as the top level of a domain if there's any other information in the domain, and the CNAME is a singleton type. BIND will refuse to accept a zone wilth multiple CNAMES for a single hostname (BIND8 had an option to allow this, but I think it was removed in BIND9.) _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
