Red Hat Bugzilla – Bug 72040
ifup-post ifup-ppp ifup should test "$PEERDNS"="yes" instead of "$PEERDNS" != "no"
Last modified: 2014-03-16 22:30:13 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020710
Description of problem:
As a result of bug #62127, redhat-config-network application
doesn't add PEERDNS='no' to ifcfg-XXX file when the option
"Automatically obtain DNS information from provider" is left
unchecked. (It adds a line PEERDNS="yes") when you check this
option, which is ok)
The scripts ifup-post, ifup-ppp) check for "$PEERDNS" != "no", and
since PEERDNS is NULL the conditional gets true and the
/etc/resolv.conf is overwritten. I have tested this
with dialup and DHCP connections
The script ifup on the other hand checks for "$PEERDNS" = "no"
in order to add the PUMPARGS and DHCPCDARGS to prevent the
overwrite of /etc/resolv.conf, it should be changed to
"$PEERDNS" != "yes"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Add or Edit a dialup, dhcp or boop device, try the option
"Automatically obtain DNS information from provider" unchecked
3.Enable/Disable this device to see changes in /etc/resolv.conf
Actual Results: The ifcfg-XXX file doesn't contain a PEERDNS='no'
line, and the /etc/resolv.conf file gets overwritten when you enable
Expected Results: When I left uncheck the "Automatically.... provider" option,
I expect to use my own DNS servers and /etc/resolv.conf should not get
The bug 62127 changes the behaviour of redhat-config-network
so it doesn't add the line PEERDNS='no'.
Maybe we should get redhat-config-network fixed instead of the
Closing bugs on older, no longer supported, releases. Apologies for any lack of
If this persists on a current release, such as Fedora Core 4, please open a new bug.