DNSimple target of DDoS attack

Bravo to the folks at DNSimple for being on top of communications during this time. It's something that they themselves brought up less then a year ago during the Zerigo DDOS (<a href="https://news.ycombinator.com/item?id=4280515" rel="nofollow">https://news.ycombinator.com/item?id=4280515</a>) so it'd good to see them sticking to it.<p>But it also seems as though the same advice proposed in that thread should have been used by their customers: Namely, utilize multiple DNS providers to mitigate risk, and choose providers with IP anycast. Heck, even setting up your own secondary DNS on a $5/mo cloud server would keep your site up (unless of course your site is the main target of the DDOS).

It's not a great long-term solution, but DNSimple has been disabling their ALIAS support, which many Heroku and AWS users are likely to depend on, especially if you use SSL.<p>Short term, keep your ALIAS record and add an additional A record for your root domain pointing to one of the IPs indicated by your hostname. DNSimple says they'll treat the A record as a fallback when ALIAS isn't working, and will return both sets of records when it is (<a href="https://twitter.com/dnsimple/status/341574753276002304" rel="nofollow">https://twitter.com/dnsimple/status/341574753276002304</a>).<p>For the next 3/12/24/96 hours or however long it takes for the threat to subside, this should increase your availability, and the likelihood that your A record will work for that time is probably reasonable. Longer term, you'll want to get rid of the A record.

Ah, got bitten by this. Just added Route 53 as redundancy, should have done that a long time ago.

DNSimple seems the best way to go if you want to host your service with Heroku using a root domain (no www at the beginning of the domain name) [1].<p>Unfortunately, DNSimple is now the weakest layer of our stack. And at <a href="http://KiteBit" rel="nofollow">http://KiteBit</a> we are suffering it right now!<p>[1]<a href="https://devcenter.heroku.com/articles/custom-domains#root-domain" rel="nofollow">https://devcenter.heroku.com/articles/custom-domains#root-do...</a>)

Our site (and others) seem to still be working through the 'www' domain. We have had nothing but great experiences with DNSimple up to this point and will probably stay customers, just sort of frustrating as we wait for our domain to resolve to another dns provider as a quick fix...

Is anyone else seeing a sustained level of trashy DNS queries to their own servers? I've been seeing a sustained level to mine that's way above normal, for the last few days. I wonder if this is a broader problem than just DNSimple.

This seems to happen quite often to DNS hosts, I remember ClouDNS getting hit often.<p>It's easier to hit these sorts of "smaller player DNS hosts" if the website you want to take down is otherwise protected?

Anyone know how to make DNS redundant? Is it as simple as adding them as extra nameservers, and then copying all the records? I'm thinking about using Linode's DNS as a failover.

That makes sense. rubygems.org was down for me for a few minutes....