[foobar2k]

There's no such thing as a quick DNS change.

[zhoutong]

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.

[Uchikoma]

Not the best advertising

http://www.nameterrific.com

"502 Bad Gateway

nginx/1.2.7"

[Nux]

Hopefully the back-end is not running Ruby. ;-)

[rdl]

The back-end is AWS Route53, it seems.

[zhoutong]

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.

[Uchikoma]

Terrific.

[zhoutong]

It's up now. Please see parent for explanation. Sorry!

[avargas]

https://www.nameterrific.com/pricing

"We're sorry, but something went wrong."

[Uchikoma]

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).

[rdl]

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.

[sturadnidge]

You should probably put the same amount of effort into your web hosting infrastructure http://imgur.com/ok5lfml

[gtklocker]

Nameterrific is down. https://www.nameterrific.com/