Thread Starter
dimal
(@dimalifragis)
Please ignore the above. I mixed up the Ips. It is correct, not 207.* what was blocked.
Apologies.
Thread Starter
dimal
(@dimalifragis)
Thread Starter
dimal
(@dimalifragis)
This could come because i see no rdns to be available? Still this is an IP of Bing.
Plugin Author
Paul
(@paultgoodchild)
We’ll take a look at this, thanks for reporting it!
Plugin Author
Paul
(@paultgoodchild)
We use the process outlined in the article below to verify Bing IP addresses:
https://www.bing.com/webmasters/help/verifying-that-bingbot-is-bingbot-3905dc26
If the Bing IP address isn’t actually resolved to a valid hostname using reverse PTR lookups, then that will cause a problem. As far I can see, it’s working correctly for that IP address now:
https://mxtoolbox.com/SuperTool.aspx?action=ptr%3a207.46.13.207
It may point to a reverse DNS resolution issue on your server? Can you check with your host whether reverse DNS is working on the server for that IP?
Plugin Author
Paul
(@paultgoodchild)
It turns out the Bing now provides a list of IP address ranges for its bots so we’ve adjusted our system to take account of those now also. This will means when/if your server has rDNS issues, it can use those Bing IPs also.
This will be available in our next release.
Thread Starter
dimal
(@dimalifragis)
Hi,
The server doesn’t suffer any dns issues, everything else shows right.
I will keep an eye open and see how it goes.
Thanks
Plugin Author
Paul
(@paultgoodchild)
Reverse DNS issues can exist even with forward DNS working normally. It definitely usually is more problematic. If your rDNS doesn’t have a problem the only reason I can see that Shield would identify this incorrectly is if there was no rDNS record available at the time. Not something we can really mitigate.
Thread Starter
dimal
(@dimalifragis)
After the issue in the log, i used
https://mxtoolbox.com/SuperTool.aspx?action=ptr%3a207.46.13.207
and there were errors returned. maybe some temp issue from their dns (msoft).
Thanks !!
Plugin Author
Paul
(@paultgoodchild)
yep, likely a temporary issue, but hopefully our latest development will reduce the risk of misidentifying their bots in the future. Thanks again for letting us know about the issue.
