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:

[main]
rc-manager=resolvconf

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

Follow

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

[main]
dns=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)

· · Web · 0 · 0 · 0
Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!