diff options
author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-07-25 15:08:29 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2016-07-25 15:08:29 -0400 |
commit | f86f6f829c3fc9544983040ec9d15bbd7df718e3 (patch) | |
tree | 18cc510b3f76256d1c8b0f1351a4a6283aa364e8 /man | |
parent | 82fda58bc3fbe21e0ff609e84d625a38e8f6cca3 (diff) | |
parent | 0b81133facb7576e983ec8427ffc3a4a8cc62846 (diff) |
Merge pull request #3802 from poettering/id128-fixes
Id128 fixes and more
Diffstat (limited to 'man')
-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 |