Closed Bug 143585 Opened 22 years ago Closed 22 years ago
Nameserver changes require restart of Mozilla
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020417 BuildID: rc1 My name server is assigned by dhcp and changes depending on which network I am using. The /etc/resolv.conf is correctly updated, but Mozilla rc1 and earlier do not notice the change. I have to restart the web user agent to have it use the new name server. Reproducible: Always Steps to Reproduce: 1. Start Mozilla 2. Change networks so that the old nameserver is no longer reachable. 3. Select a new name server (in /etc/resolv.conf) 4. Notice that Mozilla can't resolve any names. Actual Results: "www.slashdot.org not found" Expected Results: "News for Nerds. Stuff that matters." Earlier versions of Mozilla had the same problem. Netscape and lynx do notice the new nameserver.
this is a known issue *** This bug has been marked as a duplicate of 64857 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
This was fixed very recently. Please try RC2.
You need to log in before you can comment on or make changes to this bug.