On 3/31/06, Guillaume Filion <[EMAIL PROTECTED]> wrote: >I'm sold out to tinydns, it uses a (cdb) binary file for its zone files.
In my mind, what the pool needs is in terms of DNS is the sort of thing UltraDNS does. They have a geographically aware DNS load balancing service: http://www.ultradns.com/services/directional_dns.cfm Of course, someone wold have to convince them that pool.ntp.org was worthwhile enough for them to "donate" their directional DNS service to the project. I believe they run a few of the root DNS servers, so they're definitely into the idea of supporting the Internet infrastructure. Here's how another group has solved the geo-location problem in an open-source fashion using PowerDNS, but it only gets down to the country level: http://wiki.blitzed.org/DNS_balancing Finally, the people who run the free Coral content distribution network have already solved this "geographic DNS" problem, perhaps their efforts could also help us. However, I think it requires some custom code running on each node of their network, so that setup may have to be modified so that it only runs on a few "monitoring" nodes worldwide to determine network locality for all the pool time servers. http://www.coralcdn.org/pubs/ See the paper entitled "Locality Prediction for Oblivious Clients" and the "Geographic Locality of IP Prefixes". Regards, Ryan _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
