There's no such thing as a quick DNS change.
My startup NameTerrific can support instantaneous DNS updates in a geo-redundant Anycast infrastructure. As long as your TTL is sufficiently low (<300), the impact is quite limited as propagation time is negligible at NameTerrific.
EDIT: Sorry guys. We got some issues with a gem after installing the recently updated ruby2.0.0p0. The unicorn workers were timing out. TerrificDNS is completely unaffected and the site is already running again.
Hopefully the back-end is not running Ruby. ;-)
The back-end is AWS Route53, it seems.
Well, we have already soft launched our own TerrificDNS Anycast and it has replaced the Route 53 solution. TerrificDNS platform is running on Redis + PowerDNS.
Terrific.
It's up now. Please see parent for explanation. Sorry!
https://www.nameterrific.com/pricing
"We're sorry, but something went wrong."
From my experience with DNS for a large site over the last years, a lot of ISPs do not respect your TTL and have their own TTL (often 24h).
If and only if the site's end users and their software fully respects TTL. A lot don't, especially shitty mobile networks and web browsers.
Re:CloudFlare was down
by sturadnidge on Sunday March 03, 2013 @06:09AM
(#5313360)
You should probably put the same amount of effort into your web hosting infrastructure http://imgur.com/ok5lfml
Nameterrific is down. https://www.nameterrific.com/
Re:CloudFlare was down
by thomseddon on Sunday March 03, 2013 @07:46AM
(#5313540)
Would love some details on how to do this, I've been a (business) CF customer for a while now and have never seen this service and I haven't turned up anything googling/scouring their website for it just now.
Details much appreciated!
EDIT: Spoke too soon: https://support.cloudflare.com/entries/22054357-how-do-i-do-... shame it's so convoluted
That is the first time i have heard this as well. Thanks for the Link.
Yup, this CNAME service just allowed me to make a quick update to DNS and get us back up. We will probably need to automate this in the future.
When disasters like this happen, a quick DNS change can be a life-saver.