So where do you get updates on domain names from? Without that, your
packets should go to some default server somewhere. Maybe the problem
lies with THAT server, wherever it is. Do you have a router running on
your system with any sort of firewall? Like I said before, take a trip
to your local library or internet cafe and check to see if you can get
to the site from there. So far, it doesn't sound like you've done any
outside troubleshooting. All you say is "It ain't my stuff that's bad."

So until you do, most here won't take your complaint too seriously
(myself included)...





Mxsmanic wrote:

Scott writes:


Do you know what DNS stands for? It's Domain Name Server. In other
words, it is a server at your ISP that translates nemonic web addresses
into IP addresses. For example, you type http://www.dnsexample.com into
your address bar and the DNS translates that into something like
192.34.76.2. So if you are getting DNS errors the DNS at your ISP is
defective or not getting updates correctly from the network.


No. I run my own DNS nameserver, and it does not query the ISP's server (the
ISP's server is unreliable). If it cannot find a domain it will go all the
way back to the root servers, like most nameservers.