Skip to content

Commit 2f166bb

Browse files
committed
man: document _outbound
1 parent ee18f10 commit 2f166bb

File tree

3 files changed

+19
-5
lines changed

3 files changed

+19
-5
lines changed

man/nss-myhostname.xml

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,13 @@
5151
ordered by their metric. This assigns a stable hostname to the
5252
current gateway, useful for referencing it independently of the
5353
current network configuration state.</para></listitem>
54+
55+
<listitem><para>The hostname <literal>_outbound</literal> is resolved to the local IPv4 and IPv6
56+
addresses that are most likely used for communication with other hosts. This is determined by
57+
requesting a routing decision to the configured default gateways from the kernel and then using the
58+
local IP addresses selected by this decision. This hostname is only available if there is at least one
59+
local default gateway configured. This assigns a stable hostname to the local outbound IP addresses,
60+
useful for referencing them independently of the current network configuration state.</para></listitem>
5461
</itemizedlist>
5562

5663
<para>Various software relies on an always-resolvable local

man/resolvectl.xml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -299,11 +299,11 @@
299299

300300
<listitem><para>Takes a boolean parameter; used in conjunction with <command>query</command>. If true
301301
(the default), select domains are resolved on the local system, among them
302-
<literal>localhost</literal> and <literal>_gateway</literal> or entries from
303-
<filename>/etc/hosts</filename>. If false these domains are not resolved locally, and either fail (in
304-
case of <literal>localhost</literal> or <literal>_gateway</literal> and suchlike) or go to the
305-
network via regular DNS/mDNS/LLMNR lookups (in case of <filename>/etc/hosts</filename>
306-
entries).</para></listitem>
302+
<literal>localhost</literal>, <literal>_gateway</literal> and <literal>_outbound</literal>, or
303+
entries from <filename>/etc/hosts</filename>. If false these domains are not resolved locally, and
304+
either fail (in case of <literal>localhost</literal>, <literal>_gateway</literal> or
305+
<literal>_outbound</literal> and suchlike) or go to the network via regular DNS/mDNS/LLMNR lookups
306+
(in case of <filename>/etc/hosts</filename> entries).</para></listitem>
307307
</varlistentry>
308308

309309
<varlistentry>

man/systemd-resolved.service.xml

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -104,6 +104,13 @@
104104
gateway addresses, ordered by their metric. This assigns a stable hostname to the current gateway,
105105
useful for referencing it independently of the current network configuration state.</para></listitem>
106106

107+
<listitem><para>The hostname <literal>_outbound</literal> is resolved to the local IPv4 and IPv6
108+
addresses that are most likely used for communication with other hosts. This is determined by
109+
requesting a routing decision to the configured default gateways from the kernel and then using the
110+
local IP addresses selected by this decision. This hostname is only available if there is at least one
111+
local default gateway configured. This assigns a stable hostname to the local outbound IP addresses,
112+
useful for referencing them independently of the current network configuration state.</para></listitem>
113+
107114
<listitem><para>The mappings defined in <filename>/etc/hosts</filename> are resolved to their
108115
configured addresses and back, but they will not affect lookups for non-address types (like MX).
109116
Support for <filename>/etc/hosts</filename> may be disabled with <varname>ReadEtcHosts=no</varname>,

0 commit comments

Comments
 (0)