(27/07/12) Update : Mitigation of the attack continues and webforwarding solutions have been implemented. Please see https://easydns.com/2012/07/26/another-ddos-attack-against-web-forwarding/ for details
(26/07/12) Update : the DDoS has moved on to the new servers, and both are now being affected. We regret any inconvenience, and continue to work to mitigate the attack.
—————————————————–
Our apologies if this sounds a bit technical.
During a denial of service attack, one of the mitigation tactics used is to null-route packets to IP addreses which are receiving too much traffic. Due to the recent DDoS (see https://easydns.com/2012/07/25/ddos-attack-july-25-2012/) , Cogent is currently null-routing the IP address of our web-forwarding service. This means that people browsing the web that go through Cogent may experience difficulties in reaching domains that are using easyDNS for URL forwarding or Stealth forwarding.
To alleviate this matter, we have set up an alternate web-forwarder for domains who are encountering issues with this.
To swap your webforwarding over to our alternate servers, log into your easyDNS account, go to the DNS Settings tab, and select either URL or STEALTH (depending on which you use)
You will see one of the following :
or
Click the highlighted link to switch over to our alternate forwarding pool.
Cogent users should start being able to see your site shortly afterwards (depending on thier local DNS cacheing times, of course)
When you go back to this part of your account you will now see an alert as follows :
Once the DDoS is over, we’ll be providing a method to roll-back onto the primary servers, unless we come up with something more convenient or effective for our customers.
Gary Collier says
The URL forwarding isn’t working even with the change to the alternate server. Any advice?
easyDNS Support says
Hi Gary, I’ve sent you an email regarding this.
regards
Arnon (one of the easyGuys)
John says
Seems to be working for me now. Thanks guys. Will let you know if I have further problems.
Mark says
Wouldn’t have even known other than an email from Google stating Googlebot failed to reach our robots.txt file.
Switched to alternate server, working fine for now. Keep us posted.
easyDNS Support says
Thanks for the feedback. All should be ok at this point, with the new mitigation techniques.