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/resolv.conf and restarted NetworkManager to get a working configuration back.
What problem did systemd-resolved cause?
And my original question still stands, if /etc/resolv.conf is pointing to systemd-resolved, is the NM-managed dnsmasq instance actually doing anything for me?