systemd-resolved cannot be fully disabled because /etc/resolv.conf is managed about puppet-systemd HOT 3 CLOSED

Agree it would be nice to get this or someway of safely exiting systemd-resolved once it is deployed

Background is that if you stop

systemd  stop systemd-resolved

Then both of the possible targets of /etc/resolv.conf are left behind i.e

• /run/systemd/resolve/stub-resolv.conf
• /run/systemd/resolve/resolv.conf

so setting use_stuf_file => false at the same time to restore symlink to /run/systemd/resolve/resolv.conf
may seem like a good idea until you reboot and /run/systemd/resolve is not there.

In a non puppet world it would be

rm -f /etc/resolv.conf
systemctl restart NetworkManager

but that is very OS dependent of course.

How about something like

exec{'install_working_resolve_conf':
     command  => `cp /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf`
     onlyif         => `resolv.conf  is a symlink one of  /run/systemd/resolve/stub-resolv.conf or  /run/systemd/resolve/resolv.conf`
}

all a bit fiddly.

from puppet-systemd.

On the very fine point I agree when the service is stopped /etc/resolv.conf should not be managed as that is only going to end badly.

from puppet-systemd.

It feels to me like we should document that resolv.conf gets left behind and it's up to the user of this module to find some other content. As @traylenator correctly states: the replacement is not always the same. Some may end up with a static resolv.conf file, others may use NetworkManagers and there are probably a few more options out there. Trying to solve it here will just end poorly.

from puppet-systemd.