Hide Forgot
Description of problem: I have running NM. I created 00-resolv.conf as follows: $ cat /etc/NetworkManager/conf.d/00-resolv.conf [main] rc-manager=unmanaged altered /etc/resolv.conf to contain nameserver 192.168.100.1 and I rebooted thinking that everything will be correctly set on many boxes, so I can update them, etc but what I see in /etc/resolv.conf? # Generated by NetworkManager and that's it. So resolv.conf was overwritten in the meantime. Is this expected? If I call systemctl reload NetworkManager before reboot then everything works well. Do we really want to clean the resolv.conf file when NM goes down? Version-Release number of selected component (if applicable): NetworkManager-1.10.2-9.el7.x86_64
If you edit NetworkManager.conf files, without reloading the configuration (SIGHUP or via D-Bus), then the changes that you made on disk have no effect until you restart NetworkManager. Yes, this works as expected. We don't automatically reload configuration (for good reasons), so it's up to the user to do that. I'd close as NOTABUG. Regardless of that, I wonder if it ever makes sense to write an empty resolv.conf file. Maybe, if we have no name servers to configure, we should leave whatever currently is in resolv.conf file. However, that would mean, that you cannot un-configure all DNS servers if you wanted to. That doesn't seem right either. Beniamino, what do you think?
Created attachment 1393270 [details] [PATCH] dns: on quit only update resolv.conf if dns=dnsmasq
(In reply to Thomas Haller from comment #3) > If you edit NetworkManager.conf files, without reloading the configuration > (SIGHUP or via D-Bus), then the changes that you made on disk have no effect > until you restart NetworkManager. > > Yes, this works as expected. We don't automatically reload configuration > (for good reasons), so it's up to the user to do that. > > > I'd close as NOTABUG. > > > Regardless of that, I wonder if it ever makes sense to write an empty > resolv.conf file. Maybe, if we have no name servers to configure, we should > leave whatever currently is in resolv.conf file. However, that would mean, > that you cannot un-configure all DNS servers if you wanted to. That doesn't > seem right either. Beniamino, what do you think? In my opinion, the problem is that we shouldn't update resolv.conf without reason when quitting. The patch above should fix that.
(In reply to Beniamino Galvani from comment #4) > Created attachment 1393270 [details] > [PATCH] dns: on quit only update resolv.conf if dns=dnsmasq lgtm
Applied to master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=37eed6984bff6bd8dd903d480dc260005eabd132 and nm-1-10.
*** Bug 1566656 has been marked as a duplicate of this bug. ***
*** Bug 1592102 has been marked as a duplicate of this bug. ***
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://access.redhat.com/errata/RHBA-2018:3207