Finally found out how to vanquish the insidious systemd-resolved gremlins in recent Ubuntu-based distros

There's this file "/usr/lib/NetworkManager/conf.d/10-dns-resolved.conf" that you have to shadow with a file of the same name in /etc/NetworkManager/conf.d

So then, in this new file, say you want to use resolvconf again. This is the configuration:


(dpkg-reconfigure resolvconf and then reboot. resolv.conf should be correct again!)

The system shipped with this configuration, which forces systemd-resolved:


You're overriding all of this when you shadow the file.

Also, don't forget:

systemctl mask systemd-resolved && systemctl disable systemd-resolved

(oops, typos)

@yakkoj that's why I run Devuan where I can when I am working with Debian-based systems.

Sign in to participate in the conversation
Mastodon for Tech Folks

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!