Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: phranque
[edited by: phranque at 11:50 pm (utc) on Mar. 18, 2008]
[edit reason] hosting specifics [/edit]
joined:Jan 27, 2003
In particular you need to clarify the "dns server error message". Is that from your browser (Internet Explorer/Firefox)? What's the text of the error?
joined:Jan 27, 2003
my browser window res://ieframe.dll/dnserror.htm yet i can still get on the site via a proxy server
This implies that the problem may be with your internet connection rather than the site itself, or that you have inconsistent DNS.
It's actually very difficult to troubleshoot this problem without direct access to your network/website etc.
I suggest you run a DNS report [dnsreport.com] and consider using a website monitor service to check your uptime.
I suggest you run a DNS report and consider using a website monitor service to check your uptime.
Unfortunately, DNS Report is no longer free.
The moderators have been tolerant of mentioning them in the past, as it has been such a useful service for so many here.
There are other free DNS report services, but I don't know if it would be OK to mention them here. Do a search, and you will find, though.
Given that most webmasters know little about DNS, and their hosts know just a little more, it would seem essential that EVERY webmaster run a comprehensive technical DNS report on all of their domains.
I doubt that 10% do.
First things first, who provides your DNS? Your registrar or your host? (I am assuming it is not a third party, which, IMO, is almost always the best choice, but seldom used.)
if I was seeing a "dns server error message", I would try using a different dns provider.
well i would love to move in the near future but i need to sort this problem out now before i can even look at that
If the problem is beyond your control, you're not going to "sort it out".
If the problem is unreliable DNS service, moving to another DNS provider is something that can be done in a hour or so. You don't have to change your web host. It may be a quick and practical solution to the problem.
But, first, that DNS report. You're shooting in the dark right now.
If the report looks good, then I would look at connectivity issues, though you see to have eliminated that possibility. If you can ping, then it's not a connectivity issue. But how do you ping? If you do it by name (not IP address) then it is NOT a DNS issue!
Anyway, if the report looks good, I would look into using a monitoring service that can monitor your site from multiple points.