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 […]
Blog
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.
Update on status of nameservers
For the most part, things have levelled out on the DOS attack. Again, I note that most of the pain was felt by members using third party registrars who didn’t have the full 6 nameservers in their DNS delegation. Status as follows, all servers are functioning normally except certain parts of the net may have […]
DOS attack intensifies
With apologies for not posting earlier about this, but this morning the DOS attack expanded to all of our nameservers, however we have managed to maintain DNS availability. So far every single customer who has reported a problem with DNS availability over the course of the DOS attack has, upon inspection of their domain’s nameserver […]