On Tue, 2021-02-23 at 08:19 -0600, Michael Catanzaro wrote: > On Tue, Feb 23, 2021 at 10:37 am, Tadej Janež <tade...@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.
Oh, I see. Thanks for the explanation. > 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. Agreed.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
