shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-02-14 01:57:27 +03:00
Code

Fix some typos in RESOLVED-VPNS.md

Browse Source 
(cherry picked from commit 121cb88292a9cae9943c53e1d7f00c12e88293ef)
(cherry picked from commit e1b7f4af97f003fb3f822839967a438080cf33eb)
(cherry picked from commit 552c42c56085f3ccd5ba9d4bb75c8dfba77b7eaf)
This commit is contained in:
Jeremy Fleischman 2023-11-12 02:58:09 -08:00 committed by Luca Boccassi
parent d63d5b5cd0
commit 3c4bc582dc
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/RESOLVED-VPNS.md
View File

@ -48,18 +48,18 @@ a network interface may configure.
2. Routing domains: these are very similar to search domains, but are purely 2. Routing domains: these are very similar to search domains, but are purely
about DNS domain name lookup routing — they are not used for qualifying about DNS domain name lookup routing — they are not used for qualifying
single-label domain names. When it comes to routing assigning a routing single-label domain names. When it comes to routing, assigning a routing
domain to a network interface is identical to assigning a search domain to domain to a network interface is identical to assigning a search domain to
it. it.
Why the need to have both concepts, i.e. search *and* routing domains? Why the need to have both concepts, i.e. search *and* routing domains?
Mostly because in many cases the qualifying of single-label names is not Mostly because in many cases the qualifying of single-label names is not
desirable (since security-sensitive), but needs to be supported for specific desirable (as it has security implications), but needs to be supported for
use-cases. Routing domains are a concept `systemd-resolved.service` specific use-cases. Routing domains are a concept `systemd-resolved.service`
introduced, while search domains are traditionally available and are part of introduced, while search domains are traditionally available and are part of
DHCP/IPv6RA/PPP leases and thus universally supported. In many cases routing DHCP/IPv6RA/PPP leases and thus universally supported. In many cases routing
domains are probably the more appropriate concept, but not easily available, domains are probably the more appropriate concept, but not easily available,
since not part of DHCP/IPv6RA/PPP. since they are not part of DHCP/IPv6RA/PPP.
Routing domains for `systemd-resolved.service` are usually presented along Routing domains for `systemd-resolved.service` are usually presented along
with search domains in mostly the same way, but prefixed with `~` to with search domains in mostly the same way, but prefixed with `~` to
@ -79,7 +79,7 @@ a network interface may configure.
these (or sub-domains thereof) defined as routing domains, will be preferably these (or sub-domains thereof) defined as routing domains, will be preferably
used for doing reverse IP to domain name lookups. e.g. declaring used for doing reverse IP to domain name lookups. e.g. declaring
`~168.192.in-addr.arpa` on an interface means that all lookups to find the `~168.192.in-addr.arpa` on an interface means that all lookups to find the
domain names for IPv4 addresses 192.168.x.y are preferable routed to it. domain names for IPv4 addresses 192.168.x.y are preferably routed to it.
3. The `default-route` boolean. This is a simple boolean value that may be set 3. The `default-route` boolean. This is a simple boolean value that may be set
on an interface. If true (the default), any DNS lookups for which no on an interface. If true (the default), any DNS lookups for which no