Solved

Unable to reach certain websites DNS issues

Posted on 2016-10-03
3
54 Views
Last Modified: 2016-10-12
Today I started having issue with my DNS resolution and can't quite find out how to fix this issue. I have two DNS servers on my network and the primary domain controller cannot reach UPS.com but the secondary server can. On the primary server I can reach most sites but when it comes to UPS it cannot. I have restarted the server and checked the DNS settings on the NIC and all looks good however I am unable to reach UPS on that computer and since this is the primary domain controller my users cannot access the site either.

What can I do to find out what is causing this configuration error
0
Comment
Question by:tparus
3 Comments
 

Expert Comment

by:Melissa Dyer
ID: 41827179
First you need to clear the DNS cache. Run the following command: ipconfig /flushdns
Next make sure that the DNS server is using itself as the primary DNS and the secondary server is the other INTERNAL DNS server. Next verify that the forwarders setup are valid and responsive. Good luck!
0
 

Author Comment

by:tparus
ID: 41827255
Flushed the DNS and restarted both servers. The primary server can get to the UPS website but the secondary cannot. When I ping the ISP DNS servers the first server times out half the time and the secondary never times out. Could that be the issue? It really doesn't explain why one server can reach the same site while the other cannot.
0
 
LVL 26

Accepted Solution

by:
DrDave242 earned 500 total points
ID: 41828233
When I ping the ISP DNS servers the first server times out half the time and the secondary never times out. Could that be the issue?
It certainly could. If the "primary" DC has the ISP DNS servers configured as forwarders but is having issues connecting to them, it's most likely not getting responses to DNS queries that it forwards to them either.

Figuring out why you're having intermittent connectivity problems with the ISP DNS servers may be a real pain (the ISP is pretty much guaranteed to say it's not their fault, especially since your other DC doesn't seem to have the same problem), so in the meantime you may want to consider either using a different set of DNS servers as your forwarders (Google's 8.8.8.8 and 8.8.4.4, for example) or removing the forwarders altogether and using root hints instead.
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Cookie issue 7 72
Powershell: Change metric on specific adapter 6 54
web browser 3 38
Which browser works with XP 16 96
Do you come here a lot? Are you lazy like me and don't want to go through the "trouble" of having to click your Dock's Safari icon and then having to click your Experts Exchange Favorites bookmark to get here? Well then this article is for you.
Resolve DNS query failed errors for Exchange
Google currently has a new report that is in beta and coming soon to Webmaster Tool accounts. This Micro Tutorial will highlight new features for Google Webmaster Tools.
This Micro Tutorial will demonstrate how to add subdomains to your content reports. This can be very importing in having a site with multiple subdomains.

943 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

6 Experts available now in Live!

Get 1:1 Help Now