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?
What current technologies you are using to run disaster recovery? Says we
have site A and site B, if site caught a fire, all web browser will be
redirected to site B web server only.
We are planning to use round robin DNS with BGP to achieve this, is there a
better way to do this?
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.
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.