Solved

AD DNS does not resolve one specific public domain name

Posted on 2013-06-13
5
572 Views
Last Modified: 2013-07-05
We have a normal AD domain with integrated DNS that is used as DNS servers for all internal clients. Works as expected, except we now have one specific public internet domain name (one website) that will not resolve. Using other DNS servers from other domains in our internal forrest or googles public DNS servers it resolves just fine. What gives?
0
Comment
Question by:i486dx266
  • 3
  • 2
5 Comments
 
LVL 17

Expert Comment

by:LesterClayton
ID: 39243801
There are several reasons why it won't resolve, you need to check the following (NOTE: Not all may apply to your scenario):

The forwarders that the AD DNS Servers are using aren't resolving correctly.  Try change the forwarders to google's public DNS and test
The forwarders that the AD DNS Servers are using aren't resolving correctly.  Try remove all forwarders (not conditional forwarders), so that root hints are used instead
Check that you do not have a DNS zone which matches the DNS Domain (or parent domain) that you are trying to resolve
0
 

Author Comment

by:i486dx266
ID: 39244036
Hi,

Check, Check, Check. Still the same.
0
 
LVL 17

Expert Comment

by:LesterClayton
ID: 39244117
Do you have any conditional forwarders which might influence the lookup?

Could you also tell us the DNS name that you are having issues with so that we can give more specific details on what to look for.
0
 

Accepted Solution

by:
i486dx266 earned 0 total points
ID: 39252322
None that have anything to do with this domain. I could however possibly solve it by actually making a conditional forwarder for this domain name and use our ISPs DNS, bypasing our internal DNS?
0
 

Author Closing Comment

by:i486dx266
ID: 39301495
No one else gave a correct answer. This "bypass solution" ended up fixing my issue.
0

Join & Write a Comment

Occasionally you run into the website or two that will not resolve properly using your own DNS servers.  Some people simply set up global forwarders for their DNS server.  I don’t recommend doing this because it can cause problems resolving addresse…
Trying to figure out group policy inheritance and which settings apply where can be a chore.  Here's a very simple summary I've written which might help.  Keep in mind, this is just a high-level conceptual overview where I try to avoid getting bogge…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now