Quote:
Originally Posted by PamWinterReturns
My plugins do block the IP and notify me. Most block for an hour first, then twelve hours, then twenty-four hours.
A sysadmin once told me that having one hundred IPs in .htaccess would cause a serious strain on the server. I’ll block a whole network like *.bluehost.com and the block notice tells them to contact their host. Then I worked with the host to deal with hackers
Right now I have almost no traffic. Once my sites are up, I don’t want congestion from two thousand bots slowing down the box.
I’m not looking for a fix, though, just a warning site for adult webmasters and server admins
|
If you want to block at the IP level it would be better to use a firewall, which blocks connect attempts at the OS level. This is far more efficient than blocking via .htaccess, because:
1) Firewalls are optimized for blocking IP traffic. It's just masks and bits; no '*', no domains, no hostnames.
2) Blocking at the firewall level means that packets from the IP simply cannot connect to the web server port, so the web server doesn't need to waste resources receiving the request, checking htaccess, then sending back a 403 denied error.
I cannot offer you any further detail, since most of my stuff is custom, but I'm sure there are plugins that will interface with the firewall of your server's OS (probably Linux)
But if you can't figure it out, I'm reasonably confident that having 100 entries in htaccess, in 2018, will not bring your server to its knees.