Network Manager Summary

Harald Hoyer harald at
Sat Apr 5 22:42:18 UTC 2008

Dan Williams wrote:
> On Fri, 2008-04-04 at 13:55 +0200, Harald Hoyer wrote:
>> Andrew Farris wrote:
>>> Mike Chambers wrote:
>>>> On Thu, 2008-04-03 at 18:57 -0500, Mike Chambers wrote:
>>>>> BUT,  the problem seems to be, that after I set it so network didn't
>>>>> start, and network manager did, that my /etc/resolv.conf file got
>>>>> emptied and didn't have dns. I had to add it manually.  Going to reboot
>>>>> after sending this email to see if it stays this time. Or does it get
>>>>> removed each time anyway and this is a bug?
>>>> The /etc/resolv.conf file does indeed get emptied (file exists, just no
>>>> info) upon shutdown/boot up.  Although the one
>>>> in /etc/sysconfig/networking/profiles/default/resolv.conf file is filled
>>>> out but I am guessing not ready by NM.  Soooo, I thought I read about
>>>> the ifcfg-ethx file having dns info inside it?  IF so, what paramaters
>>>> are used to list it there?  DNS seems to be about the only thing so far
>>>> from NM being completely usable and no configuring at all.
>>>> Other thatn that, all is well and services seem to start.  ALTHOUGH, I
>>>> have experienced that on shutdown, while shutting down quotas, it stays
>>>> there and never goes away?  Cold boot after to get it going.
>>> Edit /etc/sysconfig/networking/devices/ifcfg-ethx and add DNS1, DNS2, 
>>> DNS3, and set PEERDNS=no and networkmanager should pick up and reset 
>>> your resolv.conf based on those cfgs and which is configured (i.e. diff 
>>> interfaces could have diff nameservers).  Also see the thread:
>>> Re: f9 resetting dns nameservers
>> NM does not seem to honor PEERDNS=no
> What's the expected behavior there for ifup?

/usr/share/doc/initscripts-*/sysconfig.txt :

       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".

PEERDNS=no : do not touch /etc/resolv.conf at all...

 >  For NM, the way it
> _should_ currently work is:
> 1) if using DHCP; DNS1..3 will override whatever the DHCP server sends
> you
> 2) if using static: you must specify DNSX or else you won't get DNS
> servers
> The problem is that we can't pull DNS servers from the existing
> resolv.conf, because stuff rewrites resolv.conf.  We need to store DNS
> information in the ifcfg files so that when more than one connection
> gets brought up, we can merge the information from both of those
> connections into a suitable resolv.conf.
> What might be a good thing to do is honor PEERDNS=no for a
> connection/ifcfg such that NM just won't use anything that an automatic
> configuration method (like DHCP or PPP) returns for that connection.
> Dan

More information about the fedora-devel-list mailing list