Bug 1093777

Summary: PEERDNS=no does not prevent from /etc/resolv.conf being overwritten
Product: Red Hat Enterprise Linux 7 Reporter: Balaji <bjayavel>
Component: initscriptsAssignee: initscripts Maintenance Team <initscripts-maint-list>
Status: CLOSED ERRATA QA Contact: Leos Pol <lpol>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.0CC: awilliam, bjayavel, dcbw, jpazdziora, jscotka, lnykryn, lpol, psimerda, rkhan, sven, thaller
Target Milestone: rcKeywords: Documentation
Target Release: 7.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: initscripts-9.49.31-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 06:41:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Balaji 2014-05-02 15:46:14 UTC
Description of problem:
With Network Manager disabled, PEERDNS setting "no" must prevent resolv.conf being overwritten for any  manual editing. 

Version-Release number of selected component (if applicable):
RHEL7.0 Beta

How reproducible:


Steps to Reproduce:
1.Disable network manager #systemctl disable NetworkManager
2.Setup networking with static IP on /etc/sysconfig/network-scripts/ifcfg-eth0
Add line "PEERDNS=no" in the end.
3.update /etc/resolv.conf with addition nameserver etc
4.systemctl restart network
5.check if the resolv.conf was overwritten

Actual results:
/etc/resolv must be preserved after reboot/network restart

Expected results:
Manual additions to /etc/resolv gets overwritten/removed

Additional info:

Comment 4 Stephen Wadeley 2014-09-11 15:00:06 UTC
See also:


How to use NetworkManager to set options in resolv.conf ?
https://access.redhat.com/solutions/61921


Why do manual changes made to '/etc/resolv.conf' files get overwritten on Red Hat Enterprise Linux ?
https://access.redhat.com/solutions/22459

Reboot removes the entries in /etc/resolv.conf.
https://access.redhat.com/solutions/513683

How do I make changes to the /etc/resolv.conf file permanent?
https://access.redhat.com/solutions/7412

Thank you

Comment 7 Laura Bailey 2015-06-26 06:41:13 UTC
This reads more like a bug than a documentation issue. Assigning to NetworkManager component; apologies if this is not the correct component.

Comment 8 Jirka Klimes 2015-06-26 08:41:37 UTC
As the reporter says in the description he disables NetworkManager, then this can't be a NetworkManager problem. But rather it is dealt by legacy initscripts.

However, I doubt there is a problem and the report should be probably closed.

PEERDNS is described in /usr/share/doc/initscripts/sysconfig.txt. And it is also mentioned in man nm-settings-ifcfg-rh, stating that there is a slight difference in behaviour when using NetworkManager.
For not touching resolv.conf during NetworkManager operation there is a configuration option dns=none (man NetworkManager.conf).

There are also useful links in comment #3 and comment #4.

Comment 9 Lukáš Nykrýn 2015-06-26 11:05:06 UTC
Can you attach you configuration?

Comment 10 Adam Williamson 2015-11-01 22:30:13 UTC
I actually seem to be seeing this problem on F23 (but was not on F21). With F23 and this /etc/sysconfig/network-scripts/ifcfg-eth0:

DEVICE="eth0"
HWADDR="XX:XX:XX:XX:XX:XX"
BOOTPROTO="dhcp"
ONBOOT="yes"
PEERDNS="no"
IPV6INIT=no
IPV6_AUTOCONF=no
DHCPV6=no

dhclient-script overwrites /etc/resolv.conf whenever the interface comes up, which PEERDNS="no" should prevent. With NetworkManager.service it seems to work correctly (resolv.conf is not overwritten).

Comment 11 Lukáš Nykrýn 2015-11-02 13:02:28 UTC
> dhclient-script overwrites /etc/resolv.conf whenever the interface comes up,
> which PEERDNS="no" should prevent. With NetworkManager.service it seems to
> work correctly (resolv.conf is not overwritten).

That looks like a completely different issue, original report is about static ip addresses. Please file separate bug for dhcp component.

Comment 12 Lukáš Nykrýn 2015-11-02 13:08:39 UTC
For the original issue, we probably need https://git.fedorahosted.org/cgit/initscripts.git/commit/?id=3d1f30095582f84206826f7ede970c45e5a6b5ba

Comment 13 Sven Hoexter 2016-03-09 09:50:00 UTC
Is there a chance we'll see this included in a point release?

Comment 15 Lukáš Nykrýn 2016-05-30 11:07:03 UTC
c471fb25f02d2e595995e7c884bbdbfe3b19ef78

Comment 19 errata-xmlrpc 2016-11-04 06:41:52 UTC
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.

https://rhn.redhat.com/errata/RHBA-2016-2456.html

Comment 20 Red Hat Bugzilla 2023-09-14 02:07:15 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days