Quote:
Originally Posted by ~Dan~
Whenever you type a url in your browser, for example www.google.com this has to be looked up on a dns server (basically it's like a big address book). The dns server tells you the ip of the url (for google it's 216.239.51.99). Without knowing the ip you (or your pc) wouldn't know whereabouts in the world the site was hosted on and so wouldn't be able to find it. DNS timeouts are where the dns server doesn't (for whatever reason) tell you the ip, so you can't go to the site.
Erm, I think this explanation is right, someone correct me if it's not.
|
LOL
Sorry, perhaps I should have been clearer and saved you a (quite good) explanation. I know what dns is (rather well in fact). I was trying to find out what problem they were experiencing, that they believed was a dns timeout. It is very rare for a dns request to timeout, and since most people don't understand dns they attribute other faults to "dns timeouts". A bit like many people blame the "proxy" server for problems that arn't actually proxy related.