Bug 1421479 - Changes to /etc/resolv.conf not persisting
Summary: Changes to /etc/resolv.conf not persisting
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 25
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-02-12 16:09 UTC by James Withers (Audere Commerce)
Modified: 2017-12-12 10:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-12 10:23:23 UTC
Type: Bug

Attachments (Terms of Use)

Description James Withers (Audere Commerce) 2017-02-12 16:09:14 UTC
Description of problem:

Changes to /etc/resolv.conf are not persisting a reboot.

How reproducible:

Every time

Steps to Reproduce:
1. Add nameserver records to /etc/resolv.conf
2. Add `PEERDNS=no` to /etc/sysconfig/network-scripts/ifcfg-eth0 (network interface)
3. Reboot

Actual results:

/etc/resolv.conf is empty

Expected results:

Entries in /etc/resolv.conf persist

Comment 1 Thomas Haller 2017-02-16 10:53:23 UTC
Assuming you are using NetworkManager.

`man nm-settings-ifcfg-rh`:

  NetworkManager had to slightly change the semantic for a few variables:

  ยท   PEERDNS - initscripts interpret PEERDNS=no to mean "never touch resolv.conf". NetworkManager interprets it to say "never add automatic (DHCP, PPP, VPN, etc.) nameservers to resolv.conf".

If you want NM not to touch resolv.conf, configure


in /etc/NetworkManager/NetworkManager.conf

Comment 2 Fedora End Of Life 2017-11-16 18:56:03 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:23:23 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.