Hacker News Reader

Man, you think you plan for everything, and then your whole TLD just stops working. What's the best way to plan for something like this?

View on HN

Have an alternate domain using completely different infrastructure.

Having a .com or .net as a backup domain, even if it isn't as sexy looking, doesn't hurt.

This may work for API endpoints but there's little re-course for your primary domain. It makes more sense to have .COM/.NET as your primary domain and have the .IO as a convenient alternative than the other way around. But my opinion is still that this is a short-term issue: the reliability of other TLDs will improve.

That's what we do at Phaxio: api.phaxio.com api.phaxio.co. We added the 'co' ever since the Zerigo DNS fiasco last year.

I'd recommend not worrying about it. You can't plan for everything and the time you spend being redundant for this (very unlikely) case is probably better spent somewhere else.

Send an email to one user asking for feedback and you will get a much better ROI than trying to plan for TLD failure.

Reply on news.ycombinator.com