Lines Matching refs:it

45    configured on it, then any lookups for names ending in `.foo.com` (or for
51    single-label domain names. When it comes to routing assigning a routing
53    it.
73    instead of `~.` — would have the same effect, but given that it's mostly
74    pointless to suffix an unqualified domain with `.`, we generally declare it
77    Routing domains also have particular relevance when it comes to the reverse
82    domain names for IPv4 addresses 192.168.x.y are preferable routed to it.
108 server, since it matches by three suffix labels instead of just two. The fact
115 ## Putting it Together
123 2. One VPN interface of the *privacy* kind, maybe called `privacy0`. When it is
127    server on it.
137    and nothing else. Finally, it might make sense to also configure a routing
156 there says so. Now, if `company0` is also upped, it will receive DNS traffic
169    have IP subnet information for the VPN, it might make sense to insert
170    `~….in-addr.arpa` and `~….ip6.arpa` reverse lookup routing domains for it.
173    value for `default-route` is actually irrelevant, but I'd set it to true. No
174    need to configure any reverse lookup routing domains for it.
227 When configuring per-interface DNS configuration settings it is wise to
229 is up `systemd-resolved.service` might start using it, and hence it's important
241 about search domains to use. In some cases it might make sense to install those
247 remote) context, contradicting user expectations. Thus it might be wise to
264 When connecting to untrusted WiFi networks it might be wise to go one step