One solution I've seen implemented is to put one nameserver in each data center, and that nameserver only responds to queries with IPs that are in that location, and sets a short TTL. So, if that center loses connectivity, no new DNS queries are being answered with IPs in the affected location. The only "lag time" is the DNS TTL. -C On Wed, Feb 06, 2002 at 09:04:19PM -0800, Doug Barton wrote:
Ken Yeo wrote:
I would like to get your comments on pros and cons on using round robin DNS to load balance web servers that are located in geographical disperse locations?
DNS isn't really designed to handle these kinds of problems, although DNS plus other technologies can. Akamai is really good at this sort of thing, you'll probably be better off working with them, since in all likelihood it'll be cheaper to work with them than to try and roll your own.
Doug -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002
Do YOU Yahoo!?
-- --------------------------- Christopher A. Woodfield rekoil@semihuman.com PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB887618B