Ubuntu
firefox package

Firefox needs a restart to refresh '/etc/resolv.conf'

Bug #32264 reported by Paul Sladen
10
Affects Status Importance Assigned to Milestone
Mozilla Firefox
Invalid
Undecided
Unassigned
firefox (Ubuntu)
Fix Released
Medium
Mozilla Bugs

Bug Description

Firefox is a web-browser installed as part of the Ubuntu interactive desktop experience. If the contents of '/etc/resolv.conf' change the Firefox does not refresh them, requiring a restart to get fresh values.

This is because Firefox has its own internal async DNS lookup system designed to be optimised and more efficient for web-browsing.

* NOTE: this needs confirming. It will be confirmed when somebody finds the offending code in 'libnss', otherwise it will be disproved...

Tags: mt-upstream
Revision history for this message
Alexandre Otto Strube (surak) wrote :

This should be posted upstream - happens with both firefox and mozilla, and both in ubuntu and fedora. Or posted against libnss this library, if it's the case - which does not match the library's package info:

"Description: Network Security Service Libraries - runtime
 This package provides the runtime libraries needed to use the Netscape
 SSL/TLS layer, including S/MIME and key management."

Revision history for this message
Paul Sladen (sladen) wrote :

Thanks for confirming this Alexandre,

Since you've observed it on both Ubuntu and Fedora, could you file it upstream on the Mozilla Bugzilla and then link it to here (Use "Link to Other Bug Tracker") in the bar at the side.

I think the code is probably more likely in 'libnspr' (Netscape Portable Runtime) than 'libnss' - thanks for reminding me.

Many Thanks,

Changed in firefox:
assignee: nobody → ijackson
status: Unconfirmed → Confirmed
Revision history for this message
Mathieu Pillard (diox) wrote :

Small tip: Although it's kinda hard to find by yourself, you can refresh the dns by switching to offline and then back to online twice.

Revision history for this message
Paul Sladen (sladen) wrote :

Mathieu: Ah, this is useful to know. Perhaps we can make any fix take advantage of this.

Ian Jackson (ijackson)
Changed in firefox:
assignee: ijackson → nobody
Revision history for this message
Alexander Sack (asac) wrote :

This is known upstream. I thought this had already been fixed, though. Anyway, Upstream triage is next step here.

Alexander Sack (asac)
Changed in firefox:
assignee: nobody → mozillateam
David Farning (dfarning)
Changed in firefox:
assignee: mozillateam → mozilla-bugs
Revision history for this message
Marco Rodrigues (gothicx) wrote :

I tried it with Firefox v2.0.0.3 at Feisty Final at it worked fine.. Changed to OpenDNS.com DNS's trought Administration -> Network and after go to http://welcome.opendns.com and it's working.

Changed in firefox:
status: Unconfirmed → Confirmed
status: Confirmed → Fix Released
status: Confirmed → Fix Released
Alexander Sack (asac)
Changed in firefox:
status: Fix Released → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.