On Tue, 14 Apr 2020 15:52:55 -0700 stan via devel devel@lists.fedoraproject.org wrote:
On Tue, 14 Apr 2020 16:18:02 -0500 Michael Catanzaro mcatanzaro@gnome.org wrote:
NetworkManager has three DNS backends: default (nss-dns, what we use currently), dnsmasq, and systemd-resolved. The default backend just does the wrong thing and cannot be fixed. When either dnsmasq or systemd-resolved is in use, NetworkManager will go ahead and do the right thing by telling dnsmasq/systemd-resolved which network interfaces should be used to resolve which hostnames. I consulted with the NetworkManager developers and they recommended systemd-resolved over dnsmasq, although I understand that dnsmasq is good too.
Will the ability to turn off NetworkManager involvement in DNS in the configuration file (None) still remain? I use a local caching DNS server, and had to do that in order to allow it to run without interference / override by NetworkManager.
Just a further note. I tried both dnsmasq and systemd-resolved, but neither seemed to work. I still saw my browser saying Looking up blah-blah.com ... and timing for seconds even if I just visited the page a few minutes before. Once I set up my own caching DNS server, that went away except when I visit a new site.