61–70 of 120 posts
Earlier quoted context omitted.
How are you exporting the zone with things as they are?
Oof, really good point – I suppose I got lucky in that I was at dnsimple.com just a few hours ago for other purposes. Their DNS was still cached for me, and it all worked flawlessly. I didn't even suspect their outage extended to their web servers, though that makes perfect sense. FWIW, the IP I have cached is 50.31.213.210.
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…
Heroku prefers you didn't use A RECORDS at all because the IP addresses in their underlying architecture might change. [1]
Earlier quoted context omitted.
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.
Well if this is an attack to get at one of DNSSimple's customers, running your own DNS would be a much easier target. Which is to say that if you were the target, you would already be hard dead by now rather than struggling as DNSSimple deploys defenses. I agree though that it is a pretty simple service to run for a small domain.
"30 minute ETA from our network provider to begin scrubbing traffic in a location with capacity." https://twitter.com/dnsimplestatus/status/539551209452232705
Unlike Dyn or CloudFlare:
Earlier quoted context omitted.
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.
Not that difficult for whom? Great if you have the in-house resources to devote to managing your own DNS (and can't put them to better use elsewhere), but that is not the case for the vast majority of us. The fact that so many of us use PaaS companies like Heroku should be a pretty big indicator that most platform-related engineering is not going to happen in-house under a certain scale.
We can watch this happen live @ http://map.ipviking.com/ Fascinating traffic floods from various locations, but the attack is not continuous.
As far as I understand, ipviking simply hosts honeypots around the world and uses those to graph "attacks" against IP blocks, etc.
I would very much like someone to correct me if this assumption is incorrect, because it'd be neat to actually watch targeted DDoS attacks, but I don't think that's what ipviking is offering.
Earlier quoted context omitted.
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.
Well if this is an attack to get at one of DNSSimple's customers, running your own DNS would be a much easier target. Which is to say that if you were the target, you would already be hard dead by now rather than struggling as DNSSimple deploys defenses. I agree though that it is a pretty simple service to run for a small domain.
But agreed, if you are the target, you're going to be hosed either way.
Earlier quoted context omitted.
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.
Not that difficult for whom? Great if you have the in-house resources to devote to managing your own DNS (and can't put them to better use elsewhere), but that is not the case for the vast majority of us. The fact that so many of us use PaaS companies like Heroku should be a pretty big indicator that most platform-related engineering is not going to happen in-house under a certain scale.
You could pay GoDaddy, Amazon Route 53, and DNSSimple to all host your records, for example... Management would be slower and manual, but people without resources for "managing your own DNS" won't be changing records that frequently anyways.
The odds of all three going down at once should help your uptime, yes?