Lines Matching refs:search

38    `systemd-resolved.service`), search domain names are attached to a system's
44    domain name lookups: if a network interface has a search domain `foo.com`
49 2. Routing domains: these are very similar to search domains, but are purely
52    domain to a network interface is identical to assigning a search domain to
55    Why the need to have both concepts, i.e. search *and* routing domains?
59    introduced, while search domains are traditionally available and are part of
65    with search domains in mostly the same way, but prefixed with `~` to
67    `foo.com` would be a configured search domain.
72    traffic is preferably routed to its DNS servers. (A search domain – i.e. `.`
75    as a routing domain, not a search domain).
86    matching routing or search domains are defined are routed to interfaces
89    search/routing domain list. An interface that has no search/routing domain
94 search/routing domains of multiple interfaces at once, then they are sent to
101 complex that what described above: if there two interfaces have search domains
106 another one `example.com` has search domain. A lookup for
132    configured. (A search domain `corp.company.example` would work too, if
134    does not provide for the concept of routing domains, but does support search
148    local WiFi router considers suitable as search domain, for example
155 domain, which will continue to go directly to `wifi0`, as the search domain
167 1. If managing a *corporate* VPN, you configure any search domains the user or
177 traditional, i.e. with any search domains as acquired, do not set `~.` though,
188    directly. Use `SetLinkDomains()` to set the per-interface search and routing
196    `resolvectl domain <iface> …` to set the search/routing domains and
232 configured DNS configuration). It is also wise to configure search/routing
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
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
257 corporate VPN of their employer, which comes with a search domain
261 had downgraded the VPN's search domain to a routing domain "~foocorp.example",
265 further even: suppress installation of search/routing domains by the network