On Mon, 2020-03-16 at 09:36 +0100, Thomas HUMMEL wrote: > > > What I don't understand is that, then if I manually remove the > > 'dns=none' setting and either restart NM and/or reload+reactivate > > the > > profile, /etc/resolv.conf is not, as I was expecting, emptied by > > NM.
Hi, I am not sure from the description. To be sure level=TRACE logging and check the logfile. But I think the reason is that NetworkManager doesn't want to write an empty /etc/resolv.conf file. If Networkmanager has no nameservers, it doesn't seem very useful to enforce that /etc/resolv.conf is empty. Either, /etc/resolv.conf is already empty, then there is no effect. Or, /etc/resolv.conf happens to contain correct name servers, then clearing the file only breaks something that otherwise would work. Or, /etc/resolv.conf contains invalid nameservers. But writing no nameservers also isn't going to make it work. best, Thomas
signature.asc
Description: This is a digitally signed message part
_______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
