Bug 128518 - NetworkManager, named and /etc/resolv.conf
Summary: NetworkManager, named and /etc/resolv.conf
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Network (show other bugs)
Version: unspecified
Hardware: i386 SuSE Linux 10.0
: P5 - None : Minor
Target Milestone: ---
Assignee: Robert Love
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-14 19:58 UTC by Gonzalo Paniagua Javier
Modified: 2005-12-05 20:10 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gonzalo Paniagua Javier 2005-10-14 19:58:37 UTC
I usually run bind (named) locally without any forwarders, so my
/etc/resolv.conf is just 'nameserver 127.0.0.1'.

Unlike dhcp after i disabled it, NetworkManager always overwrites the contents
of /etc/resolv.conf (i'm on version 0.4.1cvs20051004-3).

There should be a way of telling NM not to overwrite that file and named should
be notified whenever there's an interface/IP change too.
Comment 1 Robert Love 2005-10-17 14:23:11 UTC
I agree with the latter point -- NM should not overwrite resolv.conf if dhcp did not provide any nameservers.

But adding the named support is a lot of code for a very small minority of users who have their own local name server.
Comment 2 Gonzalo Paniagua Javier 2005-10-17 20:14:46 UTC
I thought there was already some code there in NetworkManager/src/named-manager.
Anyway, i would be happy if i can configure NM to not overwrite that file.
Thanks.
Comment 3 Robert Love 2005-10-17 20:25:47 UTC
There is -- I did not mean it was a lot of code to write, but that (since we aren't using the external named) it is a lot of overhead.  And right now it is a compile-time decision whether the external named is used, anyhow.

Anyhow, I'll fix the resolv.conf thing.
Comment 4 Robert Love 2005-10-27 20:56:13 UTC
I started on a fix for this and it is in these packages:

http://primates.ximian.com/~rml/networkmanager/RPMS/i386/

Any luck?
Comment 5 Robert Love 2005-12-05 20:10:32 UTC
This should be fixed in later releases. 20051201 is the newest.  Reopen if not.