diff options
author | Lennart Poettering <lennart@poettering.net> | 2016-07-25 20:14:13 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2016-07-25 20:14:13 +0200 |
commit | 91fe95e158405f2798997d21cb403d624e9b5578 (patch) | |
tree | 73157fc612c8437febe35b8409bd2b02b876fde7 | |
parent | 87d41d6244f1eaf441769f7f6216a606c52b8e89 (diff) |
man: minor man page fix
Addressing:
https://github.com/systemd/systemd/commit/b541146bf8c34aaaa9efcf58325f18da9253c4ec#commitcomment-17997074
-rw-r--r-- | man/systemd-resolved.service.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml index 141b06e374..aa1c2365e5 100644 --- a/man/systemd-resolved.service.xml +++ b/man/systemd-resolved.service.xml @@ -80,10 +80,10 @@ <listitem><para>Additionally, <command>systemd-resolved</command> provides a local DNS stub listener on IP address 127.0.0.53 on the local loopback interface. Programs issuing DNS requests directly, bypassing any local - API may be directed to this stub, in order to connect them <command>systemd-resolved</command>. Note however that - it is strongly recommended that local programs use the glibc NSS or bus APIs instead (as described above), as - various network resolution concepts (such as link-local addressing, or LLMNR Unicode domains) cannot be mapped to - the unicast DNS protocol.</para></listitem> + API may be directed to this stub, in order to connect them to <command>systemd-resolved</command>. Note however + that it is strongly recommended that local programs use the glibc NSS or bus APIs instead (as described above), + as various network resolution concepts (such as link-local addressing, or LLMNR Unicode domains) cannot be mapped + to the unicast DNS protocol.</para></listitem> </itemizedlist> <para>The DNS servers contacted are determined from the global settings in |