On Tue, Feb 23, 2021 at 10:37 am, Tadej Janež <tadej.j@xxxxxx> 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.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
