2018-07-02 21:15:39 +00:00
|
|
|
|
<?xml version='1.0'?>
|
2019-03-14 13:40:58 +00:00
|
|
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
2015-08-26 09:00:09 +00:00
|
|
|
|
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
|
2020-11-09 04:23:58 +00:00
|
|
|
|
<!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
|
2015-08-26 09:00:09 +00:00
|
|
|
|
|
2018-07-18 00:25:57 +00:00
|
|
|
|
<refentry id="nss-resolve" conditional='ENABLE_NSS_RESOLVE'>
|
2015-08-26 09:00:09 +00:00
|
|
|
|
|
|
|
|
|
<refentryinfo>
|
|
|
|
|
<title>nss-resolve</title>
|
|
|
|
|
<productname>systemd</productname>
|
|
|
|
|
</refentryinfo>
|
|
|
|
|
|
|
|
|
|
<refmeta>
|
|
|
|
|
<refentrytitle>nss-resolve</refentrytitle>
|
|
|
|
|
<manvolnum>8</manvolnum>
|
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
|
|
<refnamediv>
|
|
|
|
|
<refname>nss-resolve</refname>
|
|
|
|
|
<refname>libnss_resolve.so.2</refname>
|
2020-07-06 08:49:59 +00:00
|
|
|
|
<refpurpose>Hostname resolution via <filename>systemd-resolved.service</filename></refpurpose>
|
2015-08-26 09:00:09 +00:00
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
|
|
|
|
<para><filename>libnss_resolve.so.2</filename></para>
|
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Description</title>
|
|
|
|
|
|
2016-02-23 17:24:03 +00:00
|
|
|
|
<para><command>nss-resolve</command> is a plug-in module for the GNU Name Service Switch (NSS) functionality of the
|
2020-04-14 08:37:40 +00:00
|
|
|
|
GNU C Library (<command>glibc</command>) enabling it to resolve hostnames via the
|
2016-02-23 17:24:03 +00:00
|
|
|
|
<citerefentry><refentrytitle>systemd-resolved</refentrytitle><manvolnum>8</manvolnum></citerefentry> local network
|
|
|
|
|
name resolution service. It replaces the <command>nss-dns</command> plug-in module that traditionally resolves
|
|
|
|
|
hostnames via DNS.</para>
|
|
|
|
|
|
2020-04-15 16:05:39 +00:00
|
|
|
|
<para>To activate the NSS module, add <literal>resolve [!UNAVAIL=return]</literal> to the line starting
|
|
|
|
|
with <literal>hosts:</literal> in <filename>/etc/nsswitch.conf</filename>. Specifically, it is
|
|
|
|
|
recommended to place <literal>resolve</literal> early in <filename>/etc/nsswitch.conf</filename>'s
|
|
|
|
|
<literal>hosts:</literal> line. It should be before the <literal>files</literal> entry, since
|
|
|
|
|
<filename>systemd-resolved</filename> supports <filename>/etc/hosts</filename> internally, but with
|
|
|
|
|
caching. To the contrary, it should be after <literal>mymachines</literal>, to give hostnames given to
|
|
|
|
|
local VMs and containers precedence over names received over DNS. Finally, we recommend placing
|
|
|
|
|
<literal>dns</literal> somewhere after <literal>resolve</literal>, to fall back to
|
|
|
|
|
<command>nss-dns</command> if <filename>systemd-resolved.service</filename> is not available.</para>
|
2017-06-29 00:43:37 +00:00
|
|
|
|
|
2020-08-17 07:10:32 +00:00
|
|
|
|
<para>Note that <command>systemd-resolved</command> will synthesize DNS resource records in a few cases,
|
|
|
|
|
for example for <literal>localhost</literal> and the current local hostname, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-resolved</refentrytitle><manvolnum>8</manvolnum></citerefentry> for
|
|
|
|
|
the full list. This duplicates the functionality of
|
|
|
|
|
<citerefentry><refentrytitle>nss-myhostname</refentrytitle><manvolnum>8</manvolnum></citerefentry>, but
|
|
|
|
|
it is still recommended (see examples below) to keep <command>nss-myhostname</command> configured in
|
2017-06-29 00:43:37 +00:00
|
|
|
|
<filename>/etc/nsswitch.conf</filename>, to keep those names resolveable if
|
|
|
|
|
<command>systemd-resolved</command> is not running.</para>
|
2021-07-17 17:49:42 +00:00
|
|
|
|
|
|
|
|
|
<para>Please keep in mind that <command>nss-myhostname</command> (and <command>nss-resolve</command>) also resolve
|
2021-08-18 10:14:31 +00:00
|
|
|
|
in the other direction — from locally attached IP addresses to
|
2021-07-17 17:49:42 +00:00
|
|
|
|
hostnames. If you rely on that lookup being provided by DNS, you might
|
|
|
|
|
want to order things differently.
|
|
|
|
|
</para>
|
2015-08-26 09:00:09 +00:00
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Example</title>
|
|
|
|
|
|
2016-02-23 17:24:03 +00:00
|
|
|
|
<para>Here is an example <filename>/etc/nsswitch.conf</filename> file that enables <command>nss-resolve</command>
|
|
|
|
|
correctly:</para>
|
2015-08-26 09:00:09 +00:00
|
|
|
|
|
2018-11-27 16:02:20 +00:00
|
|
|
|
<!-- synchronize with other nss-* man pages and factory/etc/nsswitch.conf -->
|
2020-07-07 19:58:12 +00:00
|
|
|
|
<programlisting>passwd: compat systemd
|
2020-08-17 07:10:32 +00:00
|
|
|
|
group: compat [SUCCESS=merge] systemd
|
2021-05-05 14:11:26 +00:00
|
|
|
|
shadow: compat systemd
|
|
|
|
|
gshadow: files systemd
|
2015-08-26 09:00:09 +00:00
|
|
|
|
|
2020-08-17 07:10:32 +00:00
|
|
|
|
hosts: mymachines <command>resolve [!UNAVAIL=return]</command> files myhostname dns
|
2015-08-26 09:00:09 +00:00
|
|
|
|
networks: files
|
|
|
|
|
|
|
|
|
|
protocols: db files
|
|
|
|
|
services: db files
|
|
|
|
|
ethers: db files
|
|
|
|
|
rpc: db files
|
|
|
|
|
|
|
|
|
|
netgroup: nis</programlisting>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>See Also</title>
|
|
|
|
|
<para>
|
|
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd-resolved</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2016-07-14 17:19:49 +00:00
|
|
|
|
<citerefentry><refentrytitle>nss-systemd</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2015-08-26 09:00:09 +00:00
|
|
|
|
<citerefentry><refentrytitle>nss-myhostname</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2016-07-14 17:19:49 +00:00
|
|
|
|
<citerefentry><refentrytitle>nss-mymachines</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2015-08-26 09:00:09 +00:00
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>nsswitch.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
</para>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
</refentry>
|