Sorry about your situation.
You might enable “Block by country” on “Front-end target settings” section. In this case, reverse DNS lookup will attempt to locate a dns PTR record for an IP address by default which might possibly cause your error.
In the next release (may be 3.0.3), I’ll make this functionality disable by default and make an option for it.
Related: UA string and Qualification
Thanks for your feedback.
Thread Starter
Jakub
(@cinderellamancom)
Hi, yes I’m blocking several countries from front-end – that’s the reason of using the plugin.
Thanks
Very frequently, you know spammer and attacker disguise user agent string as google bot for example. DNS reverse lookup would effectively block those staff, but sometimes performance would be the problem.
In the current version, if you replace all HOST and HOST=... to * in “UA string and qualification” at “Front-end target settings” as follows, DNS reverse lookup would never be fetched.
Before:
Google:HOST,bot:HOST,slurp:HOST
spider:HOST,archive:HOST,*:FEED
embed.ly:HOST,Twitterbot:US,Facebot:US
After:
Google:*,bot:*,slurp:*
spider:*,archive:*,*:FEED
embed.ly:*,Twitterbot:US,Facebot:US
I hope this would be helpful for you and someone.
Hi @cinderellamancom,
Thanks for rating up your review from 1★ to 4★. I appreciate your fairness!