summaryrefslogtreecommitdiff
path: root/man/resolvectl.xml
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>2018-08-23 16:33:56 -0400
committerFilipe Brandenburger <filbranden@google.com>2018-08-23 14:47:43 -0700
commit74053ff2826df3a73cd317ac2a0606b42bc012ae (patch)
treee26a2d0888a5071cd0ad7cb454d343c8aa4807dd /man/resolvectl.xml
parentb87613ecce398a1f17e8e0e87373fdfde6bc2246 (diff)
downloadsystemd-74053ff2826df3a73cd317ac2a0606b42bc012ae.tar.gz
doc: fix resolvectl(1) per-interface DNS configuration documentation
You can only have one listitem in each varlistentry. xmllint says: resolvectl.xml:269: element varlistentry: validity error : Element varlistentry content does not follow the DTD, expecting (term+ , listitem), got (term term term term term term term listitem listitem listitem )
Diffstat (limited to 'man/resolvectl.xml')
-rw-r--r--man/resolvectl.xml37
1 files changed, 19 insertions, 18 deletions
diff --git a/man/resolvectl.xml b/man/resolvectl.xml
index cf97628f86..e07893dd15 100644
--- a/man/resolvectl.xml
+++ b/man/resolvectl.xml
@@ -247,24 +247,25 @@
<term><option>dnsovertls [<replaceable>LINK</replaceable> [<replaceable>MODE</replaceable>]]</option></term>
<term><option>nta [<replaceable>LINK</replaceable> [<replaceable>DOMAIN</replaceable>…]]</option></term>
- <listitem><para>Get/set per-interface DNS configuration. These commands may be used to configure various DNS
- settings for network interfaces that aren't managed by
- <citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>. (These
- commands will fail when used on interfaces that are managed by <command>systemd-networkd</command>, please
- configure their DNS settings directly inside the <filename>.network</filename> files instead.) These commands
- may be used to inform <command>systemd-resolved</command> about per-interface DNS configuration determined
- through external means. The <option>dns</option> command expects IPv4 or IPv6 address specifications of DNS
- servers to use. The <option>domain</option> command expects valid DNS domains, possibly prefixed with
- <literal>~</literal>, and configures a per-interface search or route-only domain. The <option>llmnr</option>,
- <option>mdns</option>, <option>dnssec</option> and <option>dnsovertls</option> commands may be used to configure
- the per-interface LLMNR, MulticastDNS, DNSSEC and DNSOverTLS settings. Finally, <option>nta</option> command
- may be used to configure additional per-interface DNSSEC NTA domains.</para></listitem>
-
- <listitem><para>Options <option>dns</option>, <option>domain</option> and <option>nta</option> can take
- a single empty string argument to clear their respective value lists.</para></listitem>
-
- <listitem><para>For details about these settings, their possible values and their effect, see the corresponding options in
- <citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
+ <listitem>
+ <para>Get/set per-interface DNS configuration. These commands may be used to configure various DNS
+ settings for network interfaces that aren't managed by
+ <citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>. (These
+ commands will fail when used on interfaces that are managed by <command>systemd-networkd</command>, please
+ configure their DNS settings directly inside the <filename>.network</filename> files instead.) These commands
+ may be used to inform <command>systemd-resolved</command> about per-interface DNS configuration determined
+ through external means. The <option>dns</option> command expects IPv4 or IPv6 address specifications of DNS
+ servers to use. The <option>domain</option> command expects valid DNS domains, possibly prefixed with
+ <literal>~</literal>, and configures a per-interface search or route-only domain. The <option>llmnr</option>,
+ <option>mdns</option>, <option>dnssec</option> and <option>dnsovertls</option> commands may be used to configure
+ the per-interface LLMNR, MulticastDNS, DNSSEC and DNSOverTLS settings. Finally, <option>nta</option> command
+ may be used to configure additional per-interface DNSSEC NTA domains.</para>
+
+ <para>Options <option>dns</option>, <option>domain</option> and <option>nta</option> can take
+ a single empty string argument to clear their respective value lists.</para>
+
+ <para>For details about these settings, their possible values and their effect, see the corresponding options in
+ <citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</listitem>
</varlistentry>