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.
wcoilAsked:
Who is Participating?
 
wcoilAuthor Commented:
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
0
 
mcsweenSr. Network AdministratorCommented:
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.

0
 
mcsweenSr. Network AdministratorCommented:
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
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
wcoilAuthor Commented:
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.
0
 
mcsweenSr. Network AdministratorCommented:
I'm curious to see if you can resolve directly through nslookup.  Try this.

start, run, nslookup
server a.b.c.d (where a.b.c.d is your ISP's dns server)
fedex.com
0
 
wcoilAuthor Commented:
nslookup using the ISP's dns resolved the address properly.

0
 
wcoilAuthor Commented:
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
0
 
wcoilAuthor Commented:
Fixed the issue.
0
 
mcsweenSr. Network AdministratorCommented:
glad you got it fixed up
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.