DNSimple target of DDoS attack
twitter.com
DNSimple target of DDoS attack
1–10 of 30 posts
Re: DNSimple target of DDoS attack
#2That makes sense. rubygems.org was down for me for a few minutes....
Re: DNSimple target of DDoS attack
#3This seems to happen quite often to DNS hosts, I remember ClouDNS getting hit often.
It's easier to hit these sorts of "smaller player DNS hosts" if the website you want to take down is otherwise protected?
Re: DNSimple target of DDoS attack
#4Ah, got bitten by this. Just added Route 53 as redundancy, should have done that a long time ago.
Re: DNSimple target of DDoS attack
#5DNSimple 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].
Unfortunately, DNSimple is now the weakest layer of our stack. And at http://KiteBit we are suffering it right now!
[1]https://devcenter.heroku.com/articles/custom-domains#root-do...)
Re: DNSimple target of DDoS attack
#6This seems to happen quite often to DNS hosts, I remember ClouDNS getting hit often. It's easier to hit these sorts of "smaller player DNS hosts" if the website you want to take down is otherwise protected?
In the three years I've been with DNSMadeEasy [0], haven't had an outage yet.
[0] https://cp.dnsmadeeasy.com/u/62796 (affiliate link)
Re: DNSimple target of DDoS attack
#7Ah, got bitten by this. Just added Route 53 as redundancy, should have done that a long time ago.
Are you doing this manually? I make solid use of DNSimple's ALIAS record type, which is also supported by Route 53, but DNSimple says they don't support AXFRs (http://support.dnsimple.com/articles/master-slave-support).
Re: DNSimple target of DDoS attack
#8Ah, got bitten by this. Just added Route 53 as redundancy, should have done that a long time ago.
[deleted]
Re: DNSimple target of DDoS attack
#9DNSimple 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]. Unfortunately, DNSimple is now the weakest layer of our stack. And at http://KiteBit we are suffering it right now! [1] https://devcenter.heroku.com/articles/custom-domains#root-do... )
Yep, I just got whacked by this at https://www.photographer.io (www is working at least). Guess I've learnt my lesson about using the root domain.
However I'm glad this happened whilst I was still beta testing! My CloudFront stack was pointing at the root domain, which was stupid. Fixed that now.
Re: DNSimple target of DDoS attack
#10Our 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...