Quote:
Originally Posted by rowan
As I said above, you need to start blocking at a less abstract level: individual IPs, or IP ranges. Firewalling at the packet level is super fast.
If you block by hostname through (say) Apache, it must do a DNS lookup in order to check against htaccess... for EVERY load. Do you really want your page to take 5 seconds to load because the user's ISP hasn't properly configured their reverse DNS?
BTW: a billion blocked IPs? That's like half the internet.
|
He said a billion IPs. I was thinking he built a supercomputer of some sort.
I notice the site page warning that I’m blocked takes about six seconds to load for me on wifi. I am not in .htaccess yet am banned. I’m whitelisted, too, but can’t get in to check if a plugin has me listed. I tried a VPN as suggested but couldn’t connect. I’ll try again later tonight.
I will ftp in and rename any login or security plugins,try to login, then see what is going on