[SOLVED] How to retain permanent manual DNS entries

[fla_panther]

I prefer to have static addressing on my LAN. I know that /etc/resolv.conf can be overwritten and the better option is to edit /etc/sysconfig/network-scripts/ifcfg-em1. What I have there is this:

Code: Select all

DEVICE=em1
HWADDR=XX:XX:XX:XX:XX:XX
TYPE=Ethernet
UUID=blahblahblahblah
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=none
IPADDR=x.x.x.x
NETMASK=255.255.255.0
GATEWAY=x.x.x.x
PEERDNS=no
DNS1=8.8.8.8
DNS2=8.8.4.4

When I reboot my server /etc/sysconfig/network-scripts/ifcfg-em1 is obviously being read because the network, mask, and gateway are all being learned as they should. But the DNS entries are ignored. I can't get online until I edit /etc/resolv.conf and put nameservers in there. Can someone explain to me why this is happening, and what i need to do to stop it from happening?

[TrevorH]

With PEERDNS=no the only person that should change /etc/resolv.conf is you. Is this your only interface?

[fla_panther]

The server has 4 ports but I'll be the only person working on the box. It seems /etc/resolv.conf is being overwritten even with PEERDNS=no.

[TrevorH]

Are you sure that one of the other interfaces isn't also up and using DHCP? PEERDNS in an ifcfg file is particular to that interface.

[fla_panther]

Strangely, all 4 ports were up despite the others being set to ONBOOT=no. I saw NM_CONTROLLED=yes on them though so I turned that off and rebooted. The other ports stayed down this time but I'm still seeing the same behaviour.

I don't know if it's worth noting here but when I first boot up if I'm quick I can load a webpage. If I wait a moment or two longer I cannot, and if I try to refresh the page I had brought up it times out. Also, I have installed squid, though it's not set up to do what I want with it yet, it's just acting as a passthough. You don't happen to know of any behaviour of squid that would wipe the /etc/resolv.conf file, do you?

[TrevorH]

Squid sounds unlikely.

What's the output from chkconfig --list | grep -i netw ?

[fla_panther]

Code: Select all

# chkconfig --list | grep -i netw
NetworkManager 	0:off	1:off	2:on	3:on	4:on	5:on	6:off
network        	0:off	1:off	2:on	3:on	4:on	5:on	6:off

[TrevorH]

Try chkconfig NetworkManager off then reboot

[fla_panther]

Yeah, that did it. Strange though, I would think that wouldn't be needed. What if I only wanted to manually manage the one port and have Network Manager do the others? I guess the stance is all one way or all the other. I could've disabled Network Manager myself but posted here because I assumed that wasn't the necessary step, that I had skipped over something in between.

[TrevorH]

NetworkManager and network are alternatives to each other and having both enabled leads to problems like this.