Forum Moderators: Robert Charlton & goodroi
Yesterday I have noticed that Reverse dns is not working when Googlebot uses a never seen before IP Range.You mention reverse DNS, but Google uses forward/reverse DNS. I'm not experienced with that to provide a detailed diagnosis, but you might be able to pick up on what's going on from several references I'm providing...
Telling webmasters to use DNS to verify on a case-by-case basis seems like the best way to go. I think the recommended technique would be to do a reverse DNS lookup, verify that the name is in the googlebot.com domain, and then do a corresponding forward DNS->IP lookup using that googlebot.com name....
....I don't think just doing a reverse DNS lookup is sufficient, because a spoofer could set up reverse DNS to point to crawl-a-b-c-d.googlebot.com
This answer has also been provided to our help-desk, so I'd consider it an official way to authenticate Googlebot. In order to fetch from the "official" Googlebot IP range, the bot has to respect robots.txt and our internal hostload conventions so that Google doesn't crawl you too hard.
With the cooperation of these search teams we were able to get CloudFlare's IP ranges are listed in a special category within search crawlers. Not only does this keep sites behind them from being clustered to a least performant denominator, or incorrectly geo-tagged based on the DNS resolution IP, it also allows the search engines to crawl at their maximum velocity since CloudFlare can handle the load without overburdening the origin.Assuming someone hosted on CloudFlare isn't trying to spoof you, I'm thinking that perhaps the CloudFlare/Googlebot combination may have issues with either the reverse DNS (or the forward/reverse DNS) you might be using.