We recently wrote a tool which can populate our DNS entries in either Route 53 or another provider (can't recall which). So if one goes down, we can run a script which brings up our DNS entires in the alternate provider.
I guess someone could service-fy this and have a meta-DNS service which let you switch backend providers.
You could leave them both live with your name server entries pointing at both as well. Then there is nothing to do if only one of them goes down. Waiting until one goes down will mean that requests aren't being served to anyone getting a cached DNS entry with references to the previous hosts.
Comments
We recently wrote a tool which can populate our DNS entries in either Route 53 or another provider (can't recall which). So if one goes down, we can run a script which brings up our DNS entires in the alternate provider.
I guess someone could service-fy this and have a meta-DNS service which let you switch backend providers.
Make it so.
You could leave them both live with your name server entries pointing at both as well. Then there is nothing to do if only one of them goes down. Waiting until one goes down will mean that requests aren't being served to anyone getting a cached DNS entry with references to the previous hosts.