Closed
Bug 864258
Opened 13 years ago
Closed 10 years ago
FF should watch /etc/resolve.conf for changes
Categories
(Core :: Networking: DNS, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: ferry, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130401133302
Steps to reproduce:
I use VPNs a lot and connect/disconnect them all the time.
FF doesn't appear to react nicely to changes in /etc/resolve.conf.
Most of the time it has problems resolving after I disconnect a VPN.
In a new window it resolves just fine, but in the windows that are already open, the old DNS server of the (closed) VPN connection appears to be used.
Expected results:
IMHO FF should (at least) watch /etc/resolve.conf for changes
|
||
Comment 1•13 years ago
|
||
A regression? bug 494969, bug 214538
Component: Untriaged → Networking: DNS
Product: Firefox → Core
|
Reporter | |
Comment 2•13 years ago
|
||
I've been having this problem for a long time.
Personally I would not consider it a regression because it always did this for as long as I remember :-(
|
||
Comment 3•10 years ago
|
||
Ferry,
Do you still see this when using a current version?
(If you do not, please close this bug as WORKSFORME or INVALID)
Flags: needinfo?(ferry)
|
|
Reporter | |
Comment 4•10 years ago
|
||
Don't think so.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(ferry)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•