On Tue, Nov 03, 2020 at 09:08:04AM -0600, Ian Pilcher wrote:
> On 11/2/20 10:37 AM, Jonathan Billings wrote:
> > 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
On 11/2/20 10:37 AM, Jonathan Billings wrote:
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/reso
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 ru
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 understan
