> the pool is unique (I would think) in the way servers can drop out of > the 'pool' and others pop back in again, with the DNS in a constant > flux. DNS was never really designed for this sort of > relative short lived records, ever constantly changing over small > periods of time. > Maybe a new era is dawning from all this...
Others have approached the issue of geographically-based servers where requests are routed to a nearby (not necessarily as the bird flies, but more as the network packet flies) server whenever possible and load balancing is done. Akamai, google, etc. do this quite effectively, but not using only DNS. They do it through colating (colocating?) servers at every network hub and doing funny tricks in the routers, mostly. But DNS is involved too. (In fact, secondary.com does clever routing to serve DNS records up!) pool.ntp.org doesn't have access to all the technical jiggery-pokery that Akamai et all have up their sleeves, but maybe we can learn something from them nevertheless. Tim. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
