Hi,
Our primary DNS on our internal net is of the Microsoft variety. A problem was brought to my attention this morning where a query to the NS for 216.239.46.66 gets an NXDOMAIN response, however a query for the address that this should resolve to (crawl3.google.com) works fine. This hostname actually resolves to about 20 IP addresses and to add an extra headache a query for most of the other IPs resolved to this hostname work fine. The server is a caching server also and upon checking the cache for the googlebot.com domain the IP above is in there with all the others for crawl3. The NS server has been setup to use external forwarders(as it's not open on port 53 for external connections, however our session based firewall should still allow queries to the forwarders)and an nslookup session on one of the forwarders resolves the above IP no probs ?? Anyone any ideas at all, any help or suggestions greatly appreciated!!!
Our primary DNS on our internal net is of the Microsoft variety. A problem was brought to my attention this morning where a query to the NS for 216.239.46.66 gets an NXDOMAIN response, however a query for the address that this should resolve to (crawl3.google.com) works fine. This hostname actually resolves to about 20 IP addresses and to add an extra headache a query for most of the other IPs resolved to this hostname work fine. The server is a caching server also and upon checking the cache for the googlebot.com domain the IP above is in there with all the others for crawl3. The NS server has been setup to use external forwarders(as it's not open on port 53 for external connections, however our session based firewall should still allow queries to the forwarders)and an nslookup session on one of the forwarders resolves the above IP no probs ?? Anyone any ideas at all, any help or suggestions greatly appreciated!!!
