Similar posting here: Windows Server 2008 - Strange DNS resolution between clients and server but the clients and servers are all using internal AD DNS servers, no external DNS Servers are setup on the nics.īoth AD DNS servers have ISP name servers setup in the Forwarders tab with 'Use root hints' UNCHECKED. ![]() If any more info is required, please let me know! It seems like this second forward lookup zone is the problem but I am not sure how or where I should be looking. Responsible mail addr = ĭoing a NSLookup on Pluto which does give the correct address: >nslookup docs.is.com.au pluto We also have a forward lookup zone of is.com.au in which docs is a CNAME also pointing to sharepoint.im.is.com.auĭoing an NSLookup on Venus the host that does not give the correct ping address results in the following: >nslookup docs.is.com.au venusġ.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa ![]() Inside of this forward lookup zone the name docs is a CNAME pointing to sharepoint.im.is.com.au Why would one DNS Server be finding the internal IP correctly and the other not and resolving to the External IP? On both servers, if I was to ping docs (without the full domain name) it resolves to the correct internal IP address. On another AD DC/DNS server (Venus) 2k8R2, we ping the same hostname and it resolves to it's external internet address of 203.2.3.4 and cannot be pinged due to the firewall doing what it is meant to do and blocking it. On one of our AD DC/DNS servers (Pluto) 2k3R2, we can ping an internal based host using it's full external hostname (docs.is.com.au) and it will resolve back to 192.168.1.210 and reply to pings - great! ![]() We have the following problem with our Windows AD DNS Servers which is in turn causing intermittent issues on our clients:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |