man: fix SendHostname= and Hostname= descriptions to allow multi-label DNS names in [DHCPv4]

This commit is contained in:
Malcolm Frazier
2026-03-09 09:42:21 +09:00
committed by Yu Watanabe
parent 2cb0ccebf6
commit 20911fe177
+8 -4
View File
@@ -2382,9 +2382,12 @@ MultiPathRoute=2001:db8::1@eth0</programlisting>
<listitem>
<para>When true (the default), the machine's hostname (or the value specified with
<varname>Hostname=</varname>, described below) will be sent to the DHCP server. Note that the
hostname must consist only of 7-bit ASCII lower-case characters and no spaces or dots, and be
formatted as a valid DNS domain name. Otherwise, the hostname is not sent even if this option
is true.</para>
hostname must consist only of 7-bit ASCII lower-case characters and no spaces, and be
formatted as a valid DNS domain name. A single-label hostname is sent as DHCP option 12
(Host Name, <ulink url="https://tools.ietf.org/html/rfc2132">RFC 2132</ulink>);
a multi-label hostname (FQDN) is sent instead as DHCP option 81 (Client FQDN,
<ulink url="https://tools.ietf.org/html/rfc4702">RFC 4702</ulink>).
Otherwise, the hostname is not sent even if this option is true.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
@@ -2395,7 +2398,8 @@ MultiPathRoute=2001:db8::1@eth0</programlisting>
<listitem>
<para>Use this value for the hostname which is sent to the DHCP server, instead of machine's
hostname. Note that the specified hostname must consist only of 7-bit ASCII lower-case
characters and no spaces or dots, and be formatted as a valid DNS domain name.</para>
characters and no spaces, and be formatted as a valid DNS domain name. Multi-label hostnames
(FQDNs) are acceptable; see <varname>SendHostname=</varname> above for details.</para>
<xi:include href="version-info.xml" xpointer="v223"/>
</listitem>