On Mi, 15.04.20 15:50, Florian Weimer (fweimer@xxxxxxxxxx) wrote: > * Lennart Poettering: > > > 1. If /etc/resolv.conf is a regular file, resolved will *consume* it > > for DNS configuration, and never change it or modify it or replace > > it. If this mode is selected arbitrary other programs that do DNS > > will talk directly to the provided DNS servers, and resolved is out > > of the loop. > > > In mode #1 resolved neither manages /etc/resolv.conf nor inserts > > itself into DNS resolution in any way. > > What will nss_resolve do in this case? Nothing? The nss_resolve module is just a wrapper around resolved's bus API. And the bus API uses resolved's own DNS resolution code. And resolved is smart enough to automatically become a *consumer* of /etc/nsswitch.conf (instead of a *manager* of it) if it is a regular file instead of a symlink to resolved's own files in /run. > Does this mean we need both resolve and dns in nsswitch.conf? Yeah, that's the idea. resolve takes control if resolved runs, and otherwise we fall back to classic nss-dns. Lennart -- Lennart Poettering, Berlin _______________________________________________ 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
