NAME<\/a> nss-resolve, libnss_resolve.so.2 \u2212 Hostname resolution via systemd\u2212resolved.service<\/p>\n libnss_resolve.so.2<\/p>\n nss\u2212resolve<\/b> is a plug\u2212in module for the GNU Name Service Switch (NSS) functionality of the GNU C Library (glibc<\/b>) enabling it to resolve hostnames via the systemd-resolved<\/b>(8) local network name resolution service. It replaces the nss\u2212dns<\/b> plug\u2212in module that traditionally resolves hostnames via DNS.<\/p>\n To activate the NSS module, add “resolve\u00a0[!UNAVAIL=return]” to the line starting with “hosts:” in \/etc\/nsswitch.conf. Specifically, it is recommended to place “resolve” early in \/etc\/nsswitch.conf’s “hosts:” line. It should be before the “files” entry, since systemd\u2212resolved supports \/etc\/hosts internally, but with caching. To the contrary, it should be after “mymachines”, to give hostnames given to local VMs and containers precedence over names received over DNS. Finally, we recommend placing “dns” somewhere after “resolve”, to fall back to nss\u2212dns<\/b> if systemd\u2212resolved.service is not available.<\/p>\n Note that systemd\u2212resolved<\/b> will synthesize DNS resource records in a few cases, for example for “localhost” and the current hostname, see systemd-resolved<\/b>(8) for the full list. This duplicates the functionality of nss-myhostname<\/b>(8), but it is still recommended (see examples below) to keep nss\u2212myhostname<\/b> configured in \/etc\/nsswitch.conf, to keep those names resolveable if systemd\u2212resolved<\/b> is not running.<\/p>\n Here is an example \/etc\/nsswitch.conf file that enables nss\u2212resolve<\/b> correctly:<\/p>\n passwd: compat systemd hosts: mymachines resolve [!UNAVAIL=return]<\/b> myhostname files dns protocols: db files netgroup: nis<\/p>\n systemd<\/b>(1), systemd-resolved<\/b>(8), nss-systemd<\/b>(8), nss-myhostname<\/b>(8), nss-mymachines<\/b>(8), nsswitch.conf<\/b>(5)<\/p>\n nss-resolve, libnss_resolve.so.2 \u2212 Hostname resolution via systemd\u2212resolved.service <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,4,203],"class_list":["post-2853","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-man8","tag-nss-resolve"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/2853","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=2853"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/2853\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=2853"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=2853"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=2853"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
SYNOPSIS<\/a>
DESCRIPTION<\/a>
EXAMPLE<\/a>
SEE ALSO<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
EXAMPLE <\/a> <\/h2>\n
group: compat systemd
shadow: compat<\/p>\n
networks: files<\/p>\n
services: db files
ethers: db files
rpc: db files<\/p>\nSEE ALSO <\/a> <\/h2>\n
\n","protected":false},"excerpt":{"rendered":"