51–60 of 120 posts
Unfortunately, it's not the first time it happens, my app is down and customers unhappy. I always wonder, why is it that someone wants to attack a small company like DNSimple ? Is it that they were blackmailed and did not surrender to the criminals? If so, why would anyone be interested in blackmailing such a small company?
DNS is so straightforward, so easily distributed, and so fundamental, that I'm always astounded when it's a single point of failure for so many operations. I wonder how many of the affected companies do have redundant appservers and load balancers, but missed this piece of the puzzle...
I'm surprised more places don't run their own DNS. It's not that difficult to do and it means you don't have to rely on another third party for service.
Earlier quoted context omitted.
My site is currently offline from this attack. I am considering that providers like DNSimple simply cannot provide the networking availability to mitigate these kinds of attacks. This is because the solution to these kinds of attacks, often, is that you need a larger pipe than the attackers. Very few people are good at both and having a huge pipe. For web apps, you can use CloudFlare, which does have a bigger pipe an…
Yes, CloudFlare has a full-featured DNS offering, even if you don't use their proxying services.
"Some DNS hosts provide a way to get CNAME-like functionality at the zone apex using a custom record type. " .. and then on to suggest DNSimple as their first suggestion.
DNS is so straightforward, so easily distributed, and so fundamental, that I'm always astounded when it's a single point of failure for so many operations. I wonder how many of the affected companies do have redundant appservers and load balancers, but missed this piece of the puzzle...
I'm surprised more places don't run their own DNS. It's not that difficult to do and it means you don't have to rely on another third party for service.
I agree though that it is a pretty simple service to run for a small domain.
If you have an active DNSimple web UI session (or API key) you can change your root nameservers by hitting their web tier directly at 50.31.213.210. We've successfully switched our domains over to nsone.net.
Anyone switching from DNSimple? I really don't want to, but we've been down for almost 3 hours. I've seen chatter about Cloudfare and it looks pretty good, reviews?
Does anyone have a simple explanation or link to an article / blog that explains the naked domain / ALIAS "problem" that DNSSimple solves? I recently set up DNS with DNSimple (due to nudging by Heroku) and am affected by this DDoS. I am still struggling to understand the exact nature of this issue. All of Heroku's documentation is pretty cryptic (to me): "Some DNS hosts provide a way to get CNAME-like functionality a…
Earlier quoted context omitted.
A few people do ALIAS style records, DNSMadeEasy and EasyDNS do "ANAME" records which are pretty much the same.
Will these services not have the same thin pipe issue that's currently affecting DNSimple?
They brag about "99.9999% uptime history" at http://www.dnsmadeeasy.com/technology/.
Though they doesn't seem as innovative and nice as DNSimple. Really hope things work out for DNSimple (really like the idea of their beta feature GitHub sync).