@ sanjeevmohindra
PS: You don’t need to be register to put the comment there..:)
My bad, all I saw was something about ‘log in to reply’. So I just came back, sorry.
Thanks Mickey for the suggestion. In fact I was thinking of removing domain name because I am not sure attack comes only from that domain.
IP I am sure and I have checked log on my server to confirm that also.
Any how its better to use as you suggested, I will change it on my guide.
Plus I believe deny based on host name requires the server to work harder then doing it my suggested way.
Here is another way you could possibly do it as well, including the other two known domains in question. Difference is no need for the ‘(www\.)?’ as leaving it out almost achieves the same effect, ‘[^.]?’ assumes any character or not after superpuperdomain (someone can correct me if I’m wrong), and I removed the ‘com’ to cover all domain suffixes.)
SetEnvIfNoCase Referer ^(superpuperdomain[^.]?|newportalse|counter-wordpress)\. ban
order allow,deny
deny from 91.220
deny from 91.196
deny from env=ban
allow from all
Not sure how much good these rules will help if the attack is using a sock and they can change their domain name and IP. I guess it could help and really wouldn’t hurt anything to use them, unless you really want that traffic from those IPs & domains and you believe it’s worth the risk. For me, I choose to be safe than sorry and I will take the chance on loosing that traffic. ??