EasyDNS is currently experiencing a Distributed Denial of Service attack, impacting ns1.easydns.com and remote2.easydns.com. Name services are currently still responding actively with the exception of the two servers listed. For maximum protection as a client of EasyDNS please ensure that you are delegated to all six of our nameservers. Current status; ns1.easydns.com – Online (null-routed […]
status
Greylisting on smtp2
Greetings, In an effort to greatly reduce the percentage of spam that manages to pass through our backup mail spools, we are implementing a greylisting system on the smtp2.easydns.com mail pool. This system will have a positive effect on legitimate mail flow, and will reduce spooling of unwanted junk mail. The impact may be an […]
The aftermath of the DOS
We are cautiously optimistic that the DOS attack has abated. We are also advised by our upstreams that at this point all null routes have been removed. If you are still experiencing visibility problems, and you know how to do the following: please email the following to support: “dig +trace “ a traceroute from where […]
current DOS attack/nameserver status
We have weathered through and in almost all cases are functioning as normal. Some domains may be experiencing a “hangover” from the attack as their ISP’s may have null routes still in place for our IP addresses. This should abate throughout the day as those ISP’s see the decreased traffic directed at us. thank you […]
current DOS attack/nameserver status
Most of the nameservers are up or worked around, as follows: ns1: up, but null routed by some carriers ns2: up remote1: sporadic remote2: up but null routed by shaw ns3: up ns6: up, rerouted The DOS attack has been ongoing and we have managed to maintain DNS availability for the most part. Some customers […]
another day, another DOS attack
The DOS attack against our nameservers resumed at approx. 5:15am EST this morning. At present ns1.easydns.com and remote1.easydns.com are being null routed by shaw but are up and visible to everyone else. Prolexic is working on mitigating the attack on ns2, remote1 and ns3 and we expect to hear back from them soon.