After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 676778 - resolv.conf gets rewritten too often
resolv.conf gets rewritten too often
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2012-05-24 21:07 UTC by Dan Williams
Modified: 2012-07-15 14:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dan Williams 2012-05-24 21:07:37 UTC 
Tore says:

Actually it seems it's not the routes being removed and re-added that causes
problems for Chrome, it is the fact that /etc/resolv.conf gets re-written -
this causes it to cancel all outstanding DNS requests. I guess NM re-activates
the entire IPv6 configuration whenever the kernel adds a routing cache entry,
which cannot be right.
Comment 1 Pavel Simerda 2012-05-27 00:02:29 UTC 
I will continue cleaning up NM IPv6 code and logging and I'm sure I will step on this bug soon.
Comment 2 Dan Winship 2012-06-26 18:14:05 UTC 
dcbw's NMDnsManager changes to only rewrite resolv.conf when something actually changed probably fixed this?
Comment 3 Tore Anderson 2012-07-15 07:09:37 UTC 
(In reply to comment #2)
> dcbw's NMDnsManager changes to only rewrite resolv.conf when something actually
> changed probably fixed this?

Yep, this is no longer a problem for me after upgrading to NetworkManager-0.9.5.95-1.git20120713 (0.9.6-rc1).