Solved

AD DNS does not resolve one specific public domain name

Posted on 2013-06-13
5
706 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 18

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 18

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

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
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…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

749 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