3 ms·
BGP. the idea is that you could have a data center in San Jose, connected via he.net, and another in, say, phoenix, connected via Cogent. you announce the sa
by lsc 17y ago
BGP. the idea is that you could have a data center in San Jose, connected via he.net, and another in, say, phoenix, connected via Cogent. you announce the same /24 out each data center... if one goes down, it stops announcing and all traffic goes to the other data center.
The problem is that it's not a cheap answer, and that your application needs to be able to deal with queries going to either data center at any time.
another option I've seen people use which is not nearly as robust but still 'automatic' is to have two authoritative nameservers; one at each location. But the nameserver at location 1 resolves all A records to IPs at location 1. At location 2, the nameserver is configured to resolve all A records to IP addresses at location 2. (of course, this has all the dns caching issues as setting the TTL to 10 minutes)
A third option would be to have some sort of redirector on a network that is made redundant via BGP, then have some sort of hook so you can change the target of the redirector. But I don't know of anyone offering that service for cheap.