/etc/resolv.conf being overwritten

[CrystalCowboy]

2.6.29.6-213.fc11.i686.PAE
NetworkManager-glib-0.7.1-8.git20090708.fc11.i586
NetworkManager-openvpn-0.7.0.99-1.fc11.i586
system-config-network-1.5.97-1.fc11.noarch
NetworkManager-openconnect-0.7.0.99-5.fc11.i586
NetworkManager-vpnc-0.7.0.99-1.fc11.i586
system-config-network-tui-1.5.97-1.fc11.noarch
NetworkManager-gnome-0.7.1-8.git20090708.fc11.i586
NetworkManager-0.7.1-8.git20090708.fc11.i586
dhclient-4.1.0-22.fc11.i586

Also happens on 64 bit:
2.6.29.6-213.fc11.x86_64

-----------------------------------------------------------------------
My /etc/resolv.conf file is being overwritten when i reboot.

NetworkManager is OFF and DISABLED.
I am NOT running DHCP.
I am using a single ethernet port configured to a static IP address.

My original /etc/resolv.conf file had several lines, a few nameservers, a "domain" line and a "search" line.

The replacement has only one non-blank line, with a single nameserver on it.
If I comment out the "DNS1" line from /etc/sysconfig/network-scripts/ifcfg-eth0, then I get a blank file for resolv.conf instead.

If I neuter /sbin/dhclient-script, and then reboot, the file does not get overwritten.

So then, since I am not using DHCP, why is /sbin/dhclient-script being run?

[SIGSEGV]

Are you using PPP?

I don't know if the sysconfig doc text file is also available on a Fedora installation.
At least on RHEL you would find such a file that roughly explains all available shell script variable definitions in /usr/share/doc/initscripts*/sysconfig.txt

You could run this to check

$ rpm -qd initscripts | grep sysconfig.txt
/usr/share/doc/initscripts-8.45.14.EL/sysconfig.txt

Therein it states that DNS{1,2} are solely for PPP enabled NIC setups,
i.e. IPPP-specific items (ISDN)

Maybe you have set PEERDNS=yes?

Originally Posted by Excerpt from sysconfig.txt

PEERDNS=yes|no
modify /etc/resolv.conf if peer uses msdns extension (PPP only) or
DNS{1,2} are set, or if using dhclient. default to "yes".
DNS{1,2}=<ip address>
provide DNS addresses that are dropped into the resolv.conf
file if PEERDNS is not set to "no".

[William Haller]

Look at /etc/sysconfig/networking/profiles/default/resolv.conf, rebuilt with system-config-network.

[CrystalCowboy]

No, I am not using PPP.

No, I did not set PEERDNS.

# rpm -qd initscripts | grep sysconfig.txt
/usr/share/doc/initscripts-8.95/sysconfig.txt

> Look at /etc/sysconfig/networking/profiles/default/resolv.conf, rebuilt with system-config-network.

I looked at it. It looks like the original I installed, not like the short form that is being overwritten.



This gets me back to my question: why is dhclient-script being run when I am not using DHCP?

[CrystalCowboy]

From /var/log/messages:
Aug 5 08:50:30 titan nm-system-settings: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Aug 5 08:50:30 titan nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ...
Aug 5 08:50:30 titan nm-system-settings: ifcfg-rh: read connection 'System eth0'
Aug 5 08:50:30 titan nm-system-settings: ifcfg-rh: Ignoring connection 'System eth0' and its device because NM_CONTROLLED was false.
Aug 5 08:50:30 titan nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...

Since I have NetworkManager turned OFF and DISABLED, why is nm-system-settings running?

[jfprieur]

I have had this happen to me as well, my resolv.conf was overwritten with one that says '#Generated by Network Manager'. Very annoying...running FC11 64-bit.

[nomisunrider]

This is REALLY annoying. I even removed Networkmanager (yum remove NetworkManager) and and still getting a "generated by networkmanager" resolv.conf

[lmgutie]

Have you guys tried turning off the "Controlled by NetworkManager" flag from system-config-network?

It helped me, but then another problem I found is that after this change the "generated by network manager" issue is replaced by "generated by /sbin/dhclient-script"; and my resulting /etc/resolv.conf is not working properly.

But if you're not using dhcp, the problem you described may go away.

[stoat]

Originally Posted by lmgutie

My problem is that after this change the "generated by network manager" issue is replaced by "generated by /sbin/dhclient-script"; my resulting /etc/resolv.conf is not working properly.

Hello lmgutie,

If you ever want to use NetworkManager to manage your connection, there is a place in the NetworkManager panel applet to enter DNS nameserver IP addresses. You can then forget about the Network Configuration utility and enter your nameservers in the IPv4 Settings tab in "Edit Connections..." of the NetworkManager panel applet. NetworkManager will then write them to /etc/resolv.conf. I use NetworkManager, and I had to do this when I first installed F11 or else Firefox, yum, and wget could not connect.

P.S.: If you've been using DHCP, then change the "Method" on the IPv4 Settings tab page to "Automatic (DHCP) addresses only". Then you will see where to enter the DNS nameserver IP addresses.

[lmgutie]

Hi Stoat,

No, I don't want to use NetworkManager. I use DHCP on a desktop computer, so I would expect system-config-network to set all that up easily for me.
From F4 to F11, dhcp had worked fine without having to deal with DNS manually, but now I'm struggling with a fresh installation.

Luis

[ferrata_vi]

Open up the following, or a similar file...

/etc/sysconfig/networking/profiles/default/ifcfg-eth0

This file, like a lot of the networking files is hard-linked in one or two other places. In that file you will find two entries...

DNS1=xxx.xxx.xxx.xxx
DNS2=xxx.xxx.xxx.xxx

If those are defined, try commenting them with hashes "#"

The system automatically rebuilds the resolv.conf from network device profiles when you boot... I think it's network manager that does it. This file is hard-linked in at least two places... /etc and /etc/sysconfig/networking/profeils/default/ If the two don't match, then you've unlinked them somehow. Either way though, the system automatically rebuilds the operative file from the settings mentioned above.

Keep in mind I'm running systems with only one interface each... no telling what happens when you config different settings on two.

[rbroberts]

Originally Posted by ferrata_vi

Keep in mind I'm running systems with only one interface each... no telling what happens when you config different settings on two.

What happens is that you pull your hair out then finally disable NetworkManager. I spent a good hour yesterday trying to figure out how to get the configuration right so that NetworkManager would not scramble my connections . This was on a clean F11 install on a host that acts as a firewall/gateway. I have two interfaces active each with aliases. I had perfectly working ifcfg-ethX files under Fedora 8 but those same configurations would not work. Until I turned of NetworkManager.

If you have only one interface and are in a setting where DCHP will assign your IP address (desktop, laptop), NetworkManager is fine (I use it on my laptop). But on my gateway, I finally did "just say no".

roland

[ferrata_vi]

Ha ha - yeah, I feel your pain. After spending a day playing with both hard-wired and wireless interfaces, I'm about to "just say no" to NetworkManager as well.

[David P]

Just to sympathise. I've just got rid of NetworkManager, the finest protection a network can get, just to have my resolv.conf broken by dhclient. You pays your money and you takes your choice. Oh for some simple documentation.

In the past I've hard coded the file and then used chattr +i /etc/resolv.conf to make it immutable. Don't change it that much anyway.

[David P]

Finally added a line to /etc/dhclient-eth0.conf

prepend domain-name "mydomain";