+++ This bug was initially created as a clone of Bug #824053 +++
Description of problem:
If /etc/resolv.conf is changed while dhclient is running (with PEERDNS=yes), /etc/resolv.conf get's overwritten even if PEERDNS was set to "no" befor it was shutdown.
Steps to Reproduce:
See bug #822930
/etc/resolv.conf is empty (or contains previous data)
/etc/resolv.conf is not touched
This is just a problem if dhclient started with PEERDNS=yes and quits with PEERDNS=no (so the user expects dhclient no to touch resolv.conf)
Comment 1 from 824053:
I already removed this /etc/resolv.conf backup&restore part of dhclient-script in F-17:
I'm closing as fixed in rawhide. Feel free to reopen if you need to have this fixed in F-16.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Any service runs dhclient (either directly or via other service), changes /etc/resolv.conf and sets PEERDNS=no in /etc/sysconfig/network-scripts/ifcfg-<iface> to prevent dhclient from editing /etc/resolv.conf. Then it stops dhclient (directly or via other service).
Dhclient rewrites /etc/resolv.conf with backup even with PEERDNS set to "no".
Code for backing up and restoring of /etc/resolv.conf was removed from dhclient-script.
dhclient doesn't rewrite /etc/resolv.conf when stopped.
Verified on RHEL6, dhclient-4.1.1-34.P1.el6.x86_64. /etc/resolv.conf isn't modified when PEERDNS set to 'no' and dhclient is stopped.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.