From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529 BuildID: 2002052918 When starting mozilla-1.0 after a new dialup connection was set up, and no other network clients (including other browsers) are uses, Mozilla will fail to connect to almost any host, claiming (popup window) "host could not be found". After sending a ping to that host (or using an other browser for it), Mozilla will proceed normaly for that host. Strange enough, the _first_ connection will mostly work. Thus, if you start at, say, google, everything will be fine. But then you will be unable to follow the links. Reproducible: Sometimes Steps to Reproduce: 1. Start a new dialup connection, don't have other clients running 2. Lunch mozilla 3. Conect to a host (www.google.com) 4. Try to follow a link pointing to another domain Actual Results: Mozilla claims "Host could not be found". Expected Results: Lookup host correctly and connect.
Are you saying that a mozilla loookup works only after doing a lookup to the same host with a different utility?
we have tons of bugs for not seeing a changed DNS, but I can't find any right now
I'm hoping to clean this up next week...
yes.. resolving as dup of bug 151683, which was opened after some still saw problems after bug 117628 -> bug 64857 were fixed. Dup'ing the "wrong way" numerically since bug 151683 is mentioned in bug 117628. *** This bug has been marked as a duplicate of 151683 ***
VERIFIED/dupe R.K.Aa: Actually you duped this the right way :) I made the "master" duplicate bug 166479, and bug 151683 points to it now. Peter created bug 151683 out of bug 117628 at my request, which I appreciate, but this problem is really confusing and bug 166479 is where the most useful information is located. Thanks for helping with this.