On Tue, Feb 23, 2021 at 10:37 am, Tadej Janež <tadej.j(a)nez.si> wrote:
I guess this is a simple solution that would work, but from what I
understand it would also disable the use of systemd-resolved?
Nah, it should just switch systemd-resolved into a consumer mode, where
it reads configuration from /etc/resolv.conf and uses that as its
source of truth. Applications using glibc for name resolution (i.e.
almost everything) will still talk to systemd-resolved and ignore
/etc/resolv.conf.
That's not the default configuration in Fedora, though. Writing to a
/etc/systemd/resolved.conf.d/*cloud-init.conf would be better though,
since it would avoid major changes to how systemd-resolved works.