On Mon, Nov 02, 2020 at 09:18:00AM -0600, Ian Pilcher wrote:
I've been using NetworkManager's dnsmasq plugin (dns=dnsmasq)
on my
laptop for years. After upgrading to Fedora 33, I see that
systemd-resolved is running (as expected), but the NetworkManager-
spawned dnsmasq instance is also running.
Is dnsmasq providing any benefit in this case? My understanding from
the earlier systemd-resolved threads is that it is supposed to handle
the "split DNS" scenario that led me to use dnsmasq in the first place.
I have a similar configuration, and at first I tried to get the
dnsmasq to be used by systemd-resolved but it kept "forgetting" it and
switching back to what DHCP used, so I just stopped, disabled and
masked systemd-resolved.service, deleted /etc/resolv.conf and
restarted NetworkManager to get a working configuration back.
--
Jonathan Billings <billings(a)negate.org>