server DNS address could not be found

Bobby
Bobby used Ask the Experts™
on
We get that error on just one particular website, ALL other websites are reachable. Using Chrome, FF, IE, none of them can get to that particular website. So, on one pc, I flushed DNS and set it to use 8.8.8.8, and then the site could be reached. We have had all our pc's set to use an internal server as the DNS server, and then that server uses 8.8.8.8. So obviously it's something with a pc pointing to an internal server as an intermediate DNS server, but again, we only have this issue with one website, and the DNS settings have been this way forever. Ideas?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
It sounds like your internal DNS server has not updated.

Author

Commented:
Updated to what? Why would just one outside website be unreachable?
That website might have changed its IP and the change in IP has not been picked up by your DNS Server.

As an experiment, try pinging the site using your DNS server and using 8.8.8.8 and see if the site is reported as having different IP addresses depending on which DNS server you are using.
11/26 Forrester Webinar: Savings for Enterprise

How can your organization benefit from savings just by replacing your legacy backup solutions with Acronis' #CyberProtection? Join Forrester's Joe Branca and Ryan Davis from Acronis live as they explain how you can too.

You can have multiple name servers listed in your local DNS configuration.  Here's a link that shows several public DNS addresses.  Adding a couple more (especially if they're from different domains) may avoid the "outage" type problem.

https://www.lifewire.com/free-and-public-dns-servers-2626062

Author

Commented:
So you guys think the website we can't get to isn't a bit shaky? It's an SEO firm I'm investigating, and the fact that I can't get to thier website was a red flag in my mind. As I said, we visit many many websites each day and this is the first time I've seen this in 15 years.
If you can reach the website when your DNS is set to Google's public server, but not when set to your private DNS server!, the fault is clearly in your DNS server, not in the site you are trying to connect to. If your DNS server does not update itself in 24 hours, you should flush its cache.
P.S., you didn't answer the question as to whether the URL resolves to a different IP address when you use your internal and Google DNS servers.

Author

Commented:
Interesting... ping that site from a pc with 8.8.8.8 as DNS and I can get there, both www and non-www. From a pc with our internal DNS, I can only ping non-www for that site. I can ping other sites, like Amazon, both www and non-www just fine. It's just that one site that won't work from our DNS server if I try with the www in front.
Does the ping that does not work resolve to a different IP to the one that works!

Author

Commented:
The ping that does not work does not resolve to any IP, so I don't know the answer to that question. I only see an IP resolve if the site is reachable.

Author

Commented:
Any other input?
Can you post a screen shot of the attempt to ping that did not work?
Also, what kind of server are you using for the DNS server?

Author

Commented:
Screenshot was taken on a Windows 7 pc.
2016-12-07_16-13-28.jpg
It appears that the URL is not in the DNS table on your DNS server. What are you using for your DNS server?

Author

Commented:
We use a local server for our DNS server, and that server uses 8.8.8.8 and 8.8.4.4
Yes, but what server? Linux, Windows? You probably need to get an admin to add this question to the forum for your server software.

Author

Commented:
Windows Server 2003 Standard SP2
CoralonSenior Citrix Engineer
Commented:
Try flushing your web cache.. I had the exact same problem last week.. I flushed the cache and everything started working.  It makes no sense to me.. but it did work :-\

Coralon
Bryon HSenior Technical Support Analyst
Top Expert 2010

Commented:
go into tour windows server, dns application and look at the forward lookup zones.  you will find the domain of the website listed there

edit it to be correct (add the right A record for www) or delete it all together
Top Expert 2004
Commented:
Also, on the client machines, try running "ipconfig /flushdns" from an administrator command prompt.
President, IT4SOHO, LLC
Commented:
Here are some steps to determine where the error might lie:
1) Goto the website http://ping.eu/nslookup & enter the domain name that is NOT resolving locally
You will see output that shows that there are 2 IPv4 addresses (and 6 IPv6 addresses) for that sample address... YOUR domain will have other results. You really only care that AT LEAST ONE IPv4 address is listed.... WRITE ALL IPv4 addresses on a note somewhere.

2) Login to your SERVER (the local DNS server) and gain an admin command prompt
You will enter the command nslookup domain server for each test
For example: nslookup www.experts-exchange.com 127.0.0.1
This example should yield a result that shows the same as the online example
When you plug in your "mystery" domain, you may find you have an answer -- or not!
If not, then you can stop looking elsewhere, your issue is in your own DNS server!

Good luck!

Dan
IT4SOHO

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial