From 36f6e87dd3e776edb81da539090d827fe3e0f82b Mon Sep 17 00:00:00 2001 From: Yu Watanabe Date: Wed, 21 Aug 2024 03:24:06 +0900 Subject: [PATCH] man: reword about default route for DNS traffic DefaultRoute is a D-Bus property, not a valid setting name in .network files nor resolved.conf. Whether a link is the default route or not is configured with DNSDefaultRoute= setting in .network files. --- man/systemd-resolved.service.xml | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml index f7be0793cf5..8d22b22e850 100644 --- a/man/systemd-resolved.service.xml +++ b/man/systemd-resolved.service.xml @@ -216,35 +216,35 @@ the traditional glibc resolver below. If a query does not match any configured routing domain (either per-link or global), it - is sent to all DNS servers that are configured on links with the DefaultRoute= - option set, as well as the globally configured DNS server. + is sent to all DNS servers that are configured on links configured as the default route, as well as the + globally configured DNS server. - If there are no DNS servers configured on any link also configured as - DefaultRoute= and no global DNS server configured, one of the compiled-in fallback - DNS servers is used. + If there are no DNS servers configured on any link also configured as the default route + and no global DNS server configured, one of the compiled-in fallback DNS servers is used. + Otherwise the unicast DNS query fails, as no suitable DNS servers can be determined. - The DefaultRoute= option is a boolean setting configurable with - resolvectl or in .network files. If not set, it is implicitly - determined based on the configured DNS domains for a link: if there's a route-only domain other than - ~., it defaults to false, otherwise to true. + Whether a link is the default route or not can be configured with + resolvectl default-route command or DNSDefaultRoute= setting in + .network files. If not configured explicitly, it is implicitly determined based on + the configured DNS domains for a link: if there's a route-only domain other than ~., + it defaults to false, otherwise to true. Effectively this means: in order to support single-label non-synthesized names, define appropriate search domains. In order to preferably route all DNS queries not explicitly matched by routing domain configuration to a specific link, configure a ~. route-only domain on it. This will ensure that other links will not be considered for these queries (unless they too carry such a routing domain). In order to route all such DNS queries to a specific link only if no other link is preferred, - set the DefaultRoute= option for the link to true and do not configure a - ~. route-only domain on it. Finally, in order to ensure that a specific link never - receives any DNS traffic not matching any of its configured routing domains, set the - DefaultRoute= option for it to false. + configure the link as the default route and do not configure a ~. route-only domain on + it. Finally, in order to ensure that a specific link never receives any DNS traffic not matching any of + its configured routing domains, make it not the default route. See org.freedesktop.resolve15 - for information about the D-Bus APIs systemd-resolved provides. + for information about the D-Bus APIs systemd-resolved provides.