"This morning’s DOS attack was directed against ns1.easydns.com … [the] rest of the nameservers … are unaffected, overall DNS availability was not affected by this attack".
I’m sure it’s not intentional, but nevertheless, that’s not the truth. Yesterday, we saw their DNS service affected on more than just that one name server. Today, at times, it’s been even worse than yesterday.
As an aside, has anyone else noticed that when a company decides to use a blog to disseminate information about mission critical services, the blog is the last thing to be looked at when there’s trouble? It’s been over 24 hours since the last update from EasyDNS; meanwhile, the DDoS on their DNS service continues without any word from them on what’s happening, what they are doing to resolve the issue, or when we can expect normal service to resume.
It doesn’t seem to have made it to the mainstream media, though, so maybe it’s not being seen elsewhere…
You’re right Andrew, we should have posted much earlier. The attack did expand across all of our nameservers this morning.
However, as we noted on the blog (just now), it looks like anybody who experienced DNS unavailability today did not have their domain delegated to the full set of nameservers here. In some cases people were delegated to only two nameservers which made the odds of losing DNS much higher during an attack such as this.
-mark