Relentless DDOS attacks on the Linode network (where we host our DNS servers) since Christmas has prompted us to relocate our secondary name server to another network. Some crazy person has been in a bad mood…
The network attacks have been a nuisance. Our secondary name server has been inaccessible once over the past week, but our primary name servers has been inaccessible for short periods of time on multiple occasions. So far, we always had at least one of the two name servers available to reply to DNS requests. You have most likely not even noticed that there was a problem.
While we have a high regard for Linode, we need mitigate the risk of a total DNS outage. For this reason we have relocated our secondary name server to the Vultr network. Again, you will most likely not even notice a difference.
The name server change is completely transparent and automatic for you; no changes are required on your side.
No we can have smile on our face when we say: Happy New Year to all!
An admistrator with the name Elize reported this afternoon that she can mot get to dashboard Also refer my problem at http://www.vanstadensrivier.ng.org.za
What must we do on our side to overcome the problem
The current ruleset of ModSecurity (our web application firewall) is blocking access to the WordPress console. It appears like the Emoji JavaScript that WordPress injects seems insecure to it.
We are in contact with Comodo (the authors of the ruleset) for a resolution. In the meantime, we suggest temporarily disabling ModSecurity for your domain from within cPanel. Do turn it on again later to ensure your website is protected against common attacks!
This issue is not related to the recent attacks on Linode and our name server maintenance.