• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Mitigating DDOS Attack

Matt Sonnentag

Basic Pleskian
One of my servers is currently under a DDOS attack. Basically we have 1000's of syn_recv packets queued for apache on port 80. We are looking for ways to mitigate this attack, so if anyone has some experience or some suggestions that would be great. The attack has been ongoing for approximately 24 hours.

Here is what we know:
Most of the attacking IPs are spoofed.
The "bot", I believe is illusion.
We know the user-agent signatures, they appear over an over from varying IPs
We have tried to block with BrowserMatch - no joy for some reason not catching it
We have tried mod_security - again no joy
mod_evasive sucks
Some joy with flood mon and blocking the various IPs with iptables
(so far we are up to about 4000 Class C's blocked)
With floodmon blocking we run about 1000-1800 queued syn-recv's from about 500 different Ips
We host at the planet and they moved us behind Cisco guard, does not seem to have even affected it.
Yes, tcp_syn cookies is on. This is not doing much good.

Any help would be appreciated!!!!!!
 
We had a few extra IP's laying around, so the ultimate goal was to figure out what site was being ddosed.

Step 1) move each to a new "staging IP", see if the attack moves
Step 2) move each site to a final "New IP"
Once we figured out the site(s), we took them offline for a week and just blocked access to the IP from the Internet.

Eventually you discover the domain being DDOSed.

You have to change ip's for your shared sites because that old IP will continue to be ddosed.
 
Back
Top