Mark Jeftovic from EasyDNS has posted a comment in response to my musings on their recent DDoS problems, and EasyDNS have also updated their blog since my first post on the subject. Looks like that trackback system works!
With regards to the setup at work, we've actually pulled the EasyDNS nameservers from our zone for the time being, and we're running on nameservers provided other providers. (Hey, that's why we pay more than one company to do the same thing.)
But why pull the EasyDNS nameservers? We had this discussion today about DNS - the idea is that, if one nameserver doesn't work, well, then you try the next one, and if that doesn't work, the next one, and so on, until you find a nameserver that does work. The problem we have at work is that all of our clients want things to load now. That means that, unfortunately, even when our domain is delegated to all 6 of the EasyDNS nameservers (as well as the other provider's nameservers), while the DDoS is going on, and EasyDNS has 2, or 3, or 4 nameservers with either slow response times, or timing out, then the DNS resolution is sometimes "slow" for our clients, when they happen to get those 2 or 3 or 4 servers in a row, and when that happens, they aren't satisfied.
Obviously, there will be times when nameservers go down. That's life, and you have to deal with it. Our clients also have to deal with the fact that, sometimes, that will mean slightly slower DNS resolution times from "normal". But it's a pain when a big provider like EasyDNS has such a widespread outage. No one can blame EasyDNS for it, but it would be nice if there was an easier way to deal with this than noting that there is a problem with your upstream nameservers (we noticed before EasyDNS first announced on the blog yesterday), and then manually removing the slow/non-responding nameservers for the period of the outage.
Is there an easier way?
