NAME<\/a> nss-myhostname, libnss_myhostname.so.2 \u2212 Hostname resolution for the locally configured system hostname<\/p>\n libnss_myhostname.so.2<\/p>\n nss\u2212myhostname<\/b> is a plug\u2212in module for the GNU Name Service Switch (NSS) functionality of the GNU C Library (glibc<\/b>), primarily providing hostname resolution for the locally configured system hostname as returned by gethostname<\/b>(2). The precise hostnames resolved by this module are:<\/p>\n \u2022 The local, configured hostname is resolved to all locally configured IP addresses ordered by their scope, or \u2014 if none are configured \u2014 the IPv4 address 127.0.0.2 (which is on the local loopback) and the IPv6 address ::1 (which is the local host).<\/p>\n \u2022 The hostnames “localhost” and “localhost.localdomain” (as well as any hostname ending in “.localhost” or “.localhost.localdomain”) are resolved to the IP addresses 127.0.0.1 and ::1.<\/p>\n \u2022 The hostname “_gateway” is resolved to all current default routing gateway addresses, ordered by their metric. This assigns a stable hostname to the current gateway, useful for referencing it independently of the current network configuration state.<\/p>\n Various software relies on an always\u2212resolvable local hostname. When using dynamic hostnames, this is traditionally achieved by patching \/etc\/hosts at the same time as changing the hostname. This is problematic since it requires a writable \/etc file system and is fragile because the file might be edited by the administrator at the same time. With nss\u2212myhostname<\/b> enabled, changing \/etc\/hosts is unnecessary, and on many systems, the file becomes entirely optional.<\/p>\n To activate the NSS modules, add “myhostname” to the line starting with “hosts:” in \/etc\/nsswitch.conf.<\/p>\n It is recommended to place “myhostname” either between “resolve” and “traditional” modules like “files” and “dns”, or after them. In the first version, well\u2212known names like “localhost” and the machine hostname are given higher priority than the external configuration. This is recommended when the external DNS servers and network are not absolutely trusted. In the second version, external configuration is given higher priority and nss\u2212myhostname<\/b> only provides a fallback mechanism. This might be suitable in closely controlled networks, for example on a company LAN.<\/p>\n Here is an example \/etc\/nsswitch.conf file that enables nss\u2212myhostname<\/b> correctly:<\/p>\n passwd: compat systemd # Either (untrusted network): protocols: db files netgroup: nis<\/p>\n To test, use glibc<\/b>‘s getent<\/b> tool:<\/p>\n $ getent ahosts \u2018hostname\u2018
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
hosts: mymachines resolve [!UNAVAIL=return] myhostname<\/b> files dns
# Or (only trusted networks):
hosts: mymachines resolve [!UNAVAIL=return] files dns myhostname<\/b>
networks: files<\/p>\n
services: db files
ethers: db files
rpc: db files<\/p>\n
::1 STREAM omega
::1 DGRAM
::1 RAW
127.0.0.2 STREAM
127.0.0.2 DGRAM
127.0.0.2 RAW<\/p>\n