Sad thing is, I want Network Manager to write my resolv.conf as it did
before. I just want systemd-resolved disabled and keep simple text file
in /etc/resolv.conf.
I haven't found automatic way to recover my system, after I do:
systemctl disable --now systemd-resolved
It keep broken /etc/resolv.conf, which I have to fix manually.
systemctl restart NetworkManager does not help.
Am I missing something?
would NetworkManager.conf:
dns=default
Write resolv.conf again? Can I make it rewrite after disabling
systemd-resolved? Why doesn't it restore /etc/resolv.conf on
systemd-resolved shutdown?
On 11/13/20 2:22 PM, Tom Horsley wrote:
(Relatively) simple fix:
systemctl stop systemd-resolvd
systemctl disable systemd-resolvd
Edit /etc/NetworkManager/NetworkManager.conf And in the [main]
section stick this:
[main]
dns=none
Now rm -f /etc/resolv.conf
Now create your own /etc/resolv.conf file from scratch with
the nameserver and search directives you actually want.
Systemd won't stick its nose in, NetworkManager won't clobber
your resolve.conf file, your network will actually function :-).
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
--
Petr Menšík
Software Engineer
Red Hat,
http://www.redhat.com/
email: pemensik(a)redhat.com
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB