What if your cloud provider is down? Use DATAPATH.IO to route your users to a healthy location while keeping your IP addresses.
Call me crazy, but I'm not sure I really care about keeping my IPs. Route 53 seems as close to bulletproof as we're going to find with DNS, and it's got cloud-independent failover routing built in. Point the primary record at your nice little EC2 server, and have the secondary record pointing as Azure or Google Cloud or your mom's laptop, whatever, and it'll do what Datapath is doing without futzing with your routing. ...right?
Comments
Call me crazy, but I'm not sure I really care about keeping my IPs. Route 53 seems as close to bulletproof as we're going to find with DNS, and it's got cloud-independent failover routing built in. Point the primary record at your nice little EC2 server, and have the secondary record pointing as Azure or Google Cloud or your mom's laptop, whatever, and it'll do what Datapath is doing without futzing with your routing. ...right?
You cannot do graceful failovers with Route 53. This is, because DNS is a system of many dependend caching layers and the TTL value is not realiable.
the TTL value is not realiable.
How is the TTL not reliable?
In my personal experience DNS cut-overs have never been a problem. Is there any major OS or ISP doing DNS wrong?
We have seen providers set the TTL value to 300 seconds no matter what. Chrome has been caching names forever while running...just two examples