Lines Matching refs:domains

10 `systemd-resolved.service` supports routing lookups for specific domains to specific
24    hosts. Only specific domains should be resolved via the VPN's DNS servers,
35 1. Search domains: these are traditional DNS configuration parameters and are
49 2. Routing domains: these are very similar to search domains, but are purely
55    Why the need to have both concepts, i.e. search *and* routing domains?
58    use-cases. Routing domains are a concept `systemd-resolved.service`
59    introduced, while search domains are traditionally available and are part of
61    domains are probably the more appropriate concept, but not easily available,
64    Routing domains for `systemd-resolved.service` are usually presented along
65    with search domains in mostly the same way, but prefixed with `~` to
71    parent domain of all domains, but itself.) When used on an interface any DNS
77    Routing domains also have particular relevance when it comes to the reverse
78    lookup DNS domains `.in-addr.arpa` and `.ip6.arpa`. An interface that has
79    these (or sub-domains thereof) defined as routing domains, will be preferably
86    matching routing or search domains are defined are routed to interfaces
94 search/routing domains of multiple interfaces at once, then they are sent to
97 interfaces are "merged": domains existing on one but not the other will "just
101 complex that what described above: if there two interfaces have search domains
134    does not provide for the concept of routing domains, but does support search
135    domains.) This interface should also set `default-route` to false, to ensure
167 1. If managing a *corporate* VPN, you configure any search domains the user or
170    `~….in-addr.arpa` and `~….ip6.arpa` reverse lookup routing domains for it.
172 2. If managing a *privacy* VPN, you include `~.` in the routing domains, the
174    need to configure any reverse lookup routing domains for it.
177 traditional, i.e. with any search domains as acquired, do not set `~.` though,
189    domains on the interfaces you manage, and `SetLinkDefaultRoute()` to manage
196    `resolvectl domain <iface> …` to set the search/routing domains and
223    `~….in-addr.arpa` or `~.ip6.arpa` routing domains.
233 domains and the `default-route` boolean *before* configuring the DNS servers,
241 about search domains to use. In some cases it might make sense to install those
242 as routing domains instead of search domains. Unqualified domain names usually
245 network.  Search domains thus generally come with security implications: they
246 might cause that unqualified domains are resolved in a different (possibly
248 downgrade *search domains* provided by VPN servers to *routing domains*, so
254 search domains: a user assumes the printer system they daily contact under the
265 further even: suppress installation of search/routing domains by the network