Fedora 10 won't remember DNS settings on reboot

Laserjock · 03-22-2009, 11:09 PM

Just set up Fedora 10 on one of my PCs and I want to use it as a web server behind my router. In the interests of full disclosure, I am a n00b.

I gave the Fedora box a static IP outside the DHCP range of my router. I then assigned the DNS servers and search path values to those I found in the status section of my router admin table. So, I am pointing to my ISP's name servers.

The settings from system-config-network are the following:

*Statically set IP addresses:
Address: 192.168.1.11
Subnet Mask: 255.255.255.0
Default gateway address: 192.168.1.1

On the DNS tab:

Hostname: <myhostname.com>
Primary DNS: <Roadrunner DNS server 1>
Secondary DNS: <Roadrunner DNS server 2>
Search Path: <Roadrunner domain>

Using these settings I can browse the interwebs just fine, and I can access my box from outside as well. However, when I reboot, I notice that all the info on my DNS tab in the network config panel has been erased and I have to enter the DNS servers in again to be able to access the interwebs. Any ideas why this is happening? Searching around, I have heard that DHCP is resetting things somehow, but I can't find a setting which would correspond to that. Another idea to is to set /etc/resolv.conf to read-only.

Any ideas? Thanks!

vindoan · 03-22-2009, 11:26 PM

Not sure why your DNS is resetting on reboot.

You can try to set the mode on the file, to ready only.

chmod a-w /etc/resolv.conf

JaksoDebr · 03-23-2009, 04:48 PM

The default installation of Fedora 10 has a buggy GUI tool for networking. It mixes up the gateway and the netmask and in the end making all networking useless. You MUST update your F10 installation with the default Fedora package updater. Note that the default installation has some problems with yum repository settings, so if you prefer to update with yum, then you must first update that one as well.

I don't know if this is in any way related to your DNS problem, but an update on all tools is suggested anyway.

Linux Archive

Laserjock · 03-24-2009, 08:33 AM

Thanks for both recommendations, unfortunately neither one worked.

Setting resolv.conf to read-only didn't last; on reboot the write bit was flipped and the DNS values were wiped out like always.

I updated everything through yum and rebooted but nothing changed.

Looks like the NetworkManager is the guilty party - simply bouncing it without rebooting the machine results in the values in resolv.conf getting wiped out. I'd like to just disable it at this point and move on with my life. Unchecking the "Controlled by NetworkManager" box just kills my network connection completely.

Anyone have a guide to disabling NetworkMangler on Fed 10 and configuring static IP manually?

fpmurphy · 03-24-2009, 09:23 AM

Run chkconfig --list. You should see the network service off and the NetworkManager service on. If this is the case, you just need to turn off NetworkManager and turn on network.

JaksoDebr · 03-24-2009, 04:45 PM

On RedHat or similar systems you can modify network settings manually by editing file /etc/sysconfig/network-scripts/ifcfg-eth0 (or any other ifcfg-ethN files, if you have more network cards).

panngo · 03-31-2009, 09:29 AM

Hi guys!
In my /etc/resolv.conf file, is typing

# Generated by NetworkManager

# No nameservers found; try putting DNS servers into your
# ifcfg files in /etc/sysconfig/network-scripts like so:
#
# DNS1=xxx.xxx.xxx.xxx
# DNS2=xxx.xxx.xxx.xxx
# DOMAIN=lab.foo.com bar.foo.com

So... to do this work, edit your ifcfg-ethX (X number of device), adding
DNS1=xxx.xxx.xxx.xxx and DNS2=xxx.xxx.xxx.xxx lines...