From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0rc1) Gecko/20020417 BuildID: 2002041711 The alert : ".... could not be found. Please check the name and try again." (dnsNotFound from global\appstrings.properties) can give the user a wrong information/advice (it can appears very often, "the name" being correct most of the times...) Reproducible: Always Steps to Reproduce: 1. use a non-automatic dialup connection 2. make sure you are not currently connected 3. ask any good HTTP address on the Internet, like "http://www.mozilla.org/" (for example) Actual Results: You get that alert Expected Results: The message should be, at least, "%s could not be found. Please make sure you are connected and the name you typed is correct. Then try again." Or, better, there should be a test to check if the DNS (or something) is reachable, before showing the message...

-> Networking

-> NEW Technically, this error is correct, because that is what DNS sends back. We don't have very good hooks in to the connection state, probably because the interfaces would be platforms specific, and these days, networking is more complicated (no more slip == dialup). This might really need to be integrated into a larger set of features that are more network aware (see bug 88218).

Since the complaint focuses on the DNS error... *** This bug has been marked as a duplicate of 164715 ***