Server 2008 R2- DNS - unable to resolve single domain - fedex.com
Windows Server 2008 R2
Active Directory
DNS
No antivirus currently installed
I am unable to resolve fedex.com. All other domains are working fine. Its only this one domain. If I statically specify our ISP's dns on a computer instead of the Domain Controller I can resolve it and browse to it. The ISP's dns servers are listed as forwarders, and use root hints is also selected. I have uninstalled and reinstalled the DNS role which did not help.
The network adapter has 127.0.0.1 for the Primary DNS. Server has been rebooted, DNS service has been restarted multiple times.
Active Directory
DNS
No antivirus currently installed
I am unable to resolve fedex.com. All other domains are working fine. Its only this one domain. If I statically specify our ISP's dns on a computer instead of the Domain Controller I can resolve it and browse to it. The ISP's dns servers are listed as forwarders, and use root hints is also selected. I have uninstalled and reinstalled the DNS role which did not help.
The network adapter has 127.0.0.1 for the Primary DNS. Server has been rebooted, DNS service has been restarted multiple times.
Bradley Fox
Try clearing the DNS Cache on the server. I'm not in front of a server right now but open dnsmgmt.msc and right click either the server node or the forward lookup zone (can't remember which) and select clear cache.
You might also try to remove cache locking on the server (set the value to 0)
http://technet.microsoft.com/en-us/library/ee649148%28WS.10%29.aspx
http://technet.microsoft.com/en-us/library/ee649148%28WS.10%29.aspx
ASKER
I cleared the cache in DNS- did not help though, still cant resolve.
I ran the command - "dnscmd /config /cachelockingpercent 0" (completed successfully) Restarted dns service, cleared cache again, ipconfig /flushdns, and tried again - did not help though, still cant resolve.
I ran the command - "dnscmd /config /cachelockingpercent 0" (completed successfully) Restarted dns service, cleared cache again, ipconfig /flushdns, and tried again - did not help though, still cant resolve.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
nslookup using the ISP's dns resolved the address properly.
ASKER
Cant Explain this, but this is what worked.
I used OpenDNS's servers as the only forwarders. And now I can resolve fedex.com
208.67.222.222
208.67.220.220
Thanks for the help mcsween
I used OpenDNS's servers as the only forwarders. And now I can resolve fedex.com
208.67.222.222
208.67.220.220
Thanks for the help mcsween
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Fixed the issue.
glad you got it fixed up