Debian Codegraph @

upstream/debian-unstable/man5/resolved.conf.5

raw
1 '\" t
2 .TH "RESOLVED\&.CONF" "5" "" "systemd 261~rc3" "resolved.conf"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 .ie \n(.g .ds Aq \(aq
11 .el .ds Aq '
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
16 .nh
17 .\" disable justification (adjust text to left margin only)
18 .ad l
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
22 .SH "NAME"
23 resolved.conf, resolved.conf.d \- Network Name Resolution configuration files
24 .SH "SYNOPSIS"
25 .PP
26 .RS 4
27 /etc/systemd/resolved\&.conf
28 .RE
29 .RS 4
30 /run/systemd/resolved\&.conf
31 .RE
32 .RS 4
33 /usr/local/lib/systemd/resolved\&.conf
34 .RE
35 .RS 4
36 /usr/lib/systemd/resolved\&.conf
37 .RE
38 .RS 4
39 /etc/systemd/resolved\&.conf\&.d/*\&.conf
40 .RE
41 .RS 4
42 /run/systemd/resolved\&.conf\&.d/*\&.conf
43 .RE
44 .RS 4
45 /usr/local/lib/systemd/resolved\&.conf\&.d/*\&.conf
46 .RE
47 .RS 4
48 /usr/lib/systemd/resolved\&.conf\&.d/*\&.conf
49 .RE
50 .SH "DESCRIPTION"
51 .PP
52 These configuration files control local DNS and LLMNR name resolution\&.
53 .SH "CONFIGURATION DIRECTORIES AND PRECEDENCE"
54 .PP
55 The default configuration is set during compilation, so configuration is only needed when it is necessary to deviate from those defaults\&. The main configuration file is loaded from one of the listed directories in order of priority, only the first file found is used:
56 /etc/systemd/,
57 /run/systemd/,
58 /usr/local/lib/systemd/
59 \&\s-2\u[1]\d\s+2,
60 /usr/lib/systemd/\&. The vendor version of the file contains commented out entries showing the defaults as a guide to the administrator\&. Local overrides can also be created by creating drop\-ins, as described below\&. The main configuration file can also be edited for this purpose (or a copy in
61 /etc/
62 if it is shipped under
63 /usr/), however using drop\-ins for local configuration is recommended over modifications to the main configuration file\&.
64 .PP
65 In addition to the main configuration file, drop\-in configuration snippets are read from
66 /usr/lib/systemd/*\&.conf\&.d/,
67 /usr/local/lib/systemd/*\&.conf\&.d/, and
68 /etc/systemd/*\&.conf\&.d/\&. Those drop\-ins have higher precedence and override the main configuration file\&. Files in the
69 *\&.conf\&.d/
70 configuration subdirectories are sorted by their filename in lexicographic order, regardless of in which of the subdirectories they reside\&. When multiple files specify the same option, for options which accept just a single value, the entry in the file sorted last takes precedence, and for options which accept a list of values, entries are collected as they occur in the sorted files\&.
71 .PP
72 When packages need to customize the configuration, they can install drop\-ins under
73 /usr/\&. Files in
74 /etc/
75 are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages\&. Drop\-ins have to be used to override package drop\-ins, since the main configuration file has lower precedence\&. It is recommended to prefix all filenames in those subdirectories with a two\-digit number and a dash, to simplify the ordering\&. This also defines a concept of drop\-in priorities to allow OS vendors to ship drop\-ins within a specific range lower than the range used by users\&. This should lower the risk of package drop\-ins overriding accidentally drop\-ins defined by users\&. It is recommended to use the range 10\-40 for drop\-ins in
76 /usr/
77 and the range 60\-90 for drop\-ins in
78 /etc/
79 and
80 /run/, to make sure that local and transient drop\-ins take priority over drop\-ins shipped by the OS vendor\&.
81 .PP
82 To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
83 /dev/null
84 in the configuration directory in
85 /etc/, with the same filename as the vendor configuration file\&.
86 .SH "OPTIONS"
87 .PP
88 The following options are available in the [Resolve] section:
89 .PP
90 \fIDNS=\fR
91 .RS 4
92 A space\-separated list of IPv4 and IPv6 addresses to use as system DNS servers\&. Each address can optionally take a port number separated with
93 ":", a network interface name or index separated with
94 "%", and a Server Name Indication (SNI) separated with
95 "#"\&. When IPv6 address is specified with a port number, then the address must be in the square brackets\&. That is, the acceptable full formats are
96 "111\&.222\&.333\&.444:9953%ifname#example\&.com"
97 for IPv4 and
98 "[1111:2222::3333]:9953%ifname#example\&.com"
99 for IPv6\&. DNS requests are sent to one of the listed DNS servers in parallel to suitable per\-link DNS servers acquired from
100 \fBsystemd-networkd.service\fR(8)
101 or set at runtime by external applications\&. For compatibility reasons, if this setting is not specified, the DNS servers listed in
102 /etc/resolv\&.conf
103 are used instead, if that file exists and any servers are configured in it\&. This setting defaults to the empty list\&.
104 .sp
105 Added in version 213\&.
106 .RE
107 .PP
108 \fIFallbackDNS=\fR
109 .RS 4
110 A space\-separated list of IPv4 and IPv6 addresses to use as the fallback DNS servers\&. Please see
111 \fIDNS=\fR
112 for acceptable format of addresses\&. Any per\-link DNS servers obtained from
113 \fBsystemd-networkd.service\fR(8)
114 take precedence over this setting, as do any servers set via
115 \fIDNS=\fR
116 above or
117 /etc/resolv\&.conf\&. This setting is hence only used if no other DNS server information is known\&. If this option is not given, a compiled\-in list of DNS servers is used instead\&.
118 .sp
119 Added in version 216\&.
120 .RE
121 .PP
122 \fIDomains=\fR
123 .RS 4
124 A space\-separated list of domains, optionally prefixed with
125 "~", used for two distinct purposes described below\&. Defaults to the empty list\&.
126 .sp
127 Any domains
128 \fInot\fR
129 prefixed with
130 "~"
131 are used as search suffixes when resolving single\-label hostnames (domain names which contain no dot), in order to qualify them into fully\-qualified domain names (FQDNs)\&. These "search domains" are strictly processed in the order they are specified in, until the name with the suffix appended is found\&. For compatibility reasons, if this setting is not specified, the search domains listed in
132 /etc/resolv\&.conf
133 with the
134 \fIsearch\fR
135 keyword are used instead, if that file exists and any domains are configured in it\&.
136 .sp
137 The domains prefixed with
138 "~"
139 are called "route\-only domains"\&. All domains listed here (\fIboth search domains and route\-only domains\fR
140 after removing the
141 "~"
142 prefix) define a search path that preferably directs DNS queries to this interface\&. This search path has an effect only when suitable per\-link DNS servers are known\&. Such servers may be defined through the
143 \fIDNS=\fR
144 setting (see above) and dynamically at run time, for example from DHCP leases\&. If no per\-link DNS servers are known, route\-only domains have no effect\&.
145 .sp
146 Use the construct
147 "~\&."
148 (which is composed from
149 "~"
150 to indicate a route\-only domain and
151 "\&."
152 to indicate the DNS root domain that is the implied suffix of all DNS domains) to use the DNS servers defined for this link preferably for all domains\&.
153 .sp
154 See "Protocols and Routing" in
155 \fBsystemd-resolved.service\fR(8)
156 for details of how search and route\-only domains are used\&.
157 .sp
158 Note that configuring the MulticastDNS domain
159 "local"
160 as search or routing domain has the effect of routing lookups for this domain to classic unicast DNS\&. This may be used to provide compatibility with legacy installations that use this domain in a unicast DNS context, against the IANA assignment of this domain to pure MulticastDNS purposes\&. Search and routing domains are a unicast DNS concept, they
161 \fIcannot\fR
162 be used to resolve single\-label lookups via MulticastDNS\&.
163 .sp
164 Added in version 229\&.
165 .RE
166 .PP
167 \fILLMNR=\fR
168 .RS 4
169 Takes a boolean argument or
170 "resolve"\&. Controls Link\-Local Multicast Name Resolution support (\m[blue]\fBRFC 4795\fR\m[]\&\s-2\u[2]\d\s+2) on the local host\&. If true, enables full LLMNR responder and resolver support\&. If false, disables both\&. If set to
171 "resolve", only resolution support is enabled, but responding is disabled\&. Note that
172 \fBsystemd-networkd.service\fR(8)
173 also maintains per\-link LLMNR settings\&. LLMNR will be enabled on a link only if the per\-link and the global setting is on\&.
174 .sp
175 Added in version 216\&.
176 .RE
177 .PP
178 \fIMulticastDNS=\fR
179 .RS 4
180 Takes a boolean argument or
181 "resolve"\&. Controls Multicast DNS support (\m[blue]\fBRFC 6762\fR\m[]\&\s-2\u[3]\d\s+2) on the local host\&. If true, enables full Multicast DNS responder and resolver support\&. If false, disables both\&. If set to
182 "resolve", only resolution support is enabled, but responding is disabled\&. Note that
183 \fBsystemd-networkd.service\fR(8)
184 also maintains per\-link Multicast DNS settings\&. Multicast DNS will be enabled on a link only if the per\-link and the global setting is on\&.
185 .sp
186 Added in version 234\&.
187 .RE
188 .PP
189 \fIDNSSEC=\fR
190 .RS 4
191 Takes a boolean argument or
192 "allow\-downgrade"\&.
193 .sp
194 If set to true, all DNS lookups are DNSSEC\-validated locally (excluding LLMNR and Multicast DNS)\&. If the response to a lookup request is detected to be invalid a lookup failure is returned to applications\&. Note that this mode requires a DNS server that supports DNSSEC\&. If the DNS server does not properly support DNSSEC all validations will fail\&.
195 .sp
196 If set to
197 "allow\-downgrade", DNSSEC validation is attempted, but if the server does not support DNSSEC properly, DNSSEC mode is automatically disabled\&. Note that this mode makes DNSSEC validation vulnerable to "downgrade" attacks, where an attacker might be able to trigger a downgrade to non\-DNSSEC mode by synthesizing a DNS response that suggests DNSSEC was not supported\&.
198 .sp
199 If set to false, DNS lookups are not DNSSEC validated\&.
200 .sp
201 Note that DNSSEC validation requires retrieval of additional DNS data, and thus results in a small DNS lookup time penalty\&.
202 .sp
203 DNSSEC requires knowledge of "trust anchors" to prove data integrity\&. The trust anchor for the Internet root domain is built into the resolver, additional trust anchors may be defined with
204 \fBdnssec-trust-anchors.d\fR(5)\&. Trust anchors may change at regular intervals, and old trust anchors may be revoked\&. In such a case DNSSEC validation is not possible until new trust anchors are configured locally or the resolver software package is updated with the new root trust anchor\&. In effect, when the built\-in trust anchor is revoked and
205 \fIDNSSEC=\fR
206 is true, all further lookups will fail, as it cannot be proved anymore whether lookups are correctly signed, or validly unsigned\&. If
207 \fIDNSSEC=\fR
208 is set to
209 "allow\-downgrade"
210 the resolver will automatically turn off DNSSEC validation in such a case\&.
211 .sp
212 Client programs looking up DNS data will be informed whether lookups could be verified using DNSSEC, or whether the returned data could not be verified (either because the data was found unsigned in the DNS, or the DNS server did not support DNSSEC or no appropriate trust anchors were known)\&. In the latter case, it is assumed that client programs employ a secondary scheme to validate the returned DNS data, should this be required\&.
213 .sp
214 It is recommended to set
215 \fIDNSSEC=\fR
216 to true on systems where it is known that the DNS server supports DNSSEC correctly, and where software or trust anchor updates happen regularly\&. On other systems it is recommended to set
217 \fIDNSSEC=\fR
218 to
219 "allow\-downgrade"\&.
220 .sp
221 In addition to this global DNSSEC setting
222 \fBsystemd-networkd.service\fR(8)
223 also maintains per\-link DNSSEC settings\&. For system DNS servers (see above), only the global DNSSEC setting is in effect\&. For per\-link DNS servers the per\-link setting is in effect, unless it is unset in which case the global setting is used instead\&.
224 .sp
225 Site\-private DNS zones generally conflict with DNSSEC operation, unless a negative (if the private zone is not signed) or positive (if the private zone is signed) trust anchor is configured for them\&. If
226 "allow\-downgrade"
227 mode is selected, it is attempted to detect site\-private DNS zones using top\-level domains (TLDs) that are not known by the DNS root server\&. This logic does not work in all private zone setups\&.
228 .sp
229 Defaults to
230 "no"\&.
231 .sp
232 Added in version 229\&.
233 .RE
234 .PP
235 \fIDNSOverTLS=\fR
236 .RS 4
237 Takes a boolean argument or
238 "opportunistic"\&. If true all connections to the server will be encrypted\&. Note that this mode requires a DNS server that supports DNS\-over\-TLS and has a valid certificate\&. If the hostname was specified in
239 \fIDNS=\fR
240 by using the format
241 "address#server_name"
242 it is used to validate its certificate and also to enable Server Name Indication (SNI) when opening a TLS connection\&. Otherwise the certificate is checked against the server\*(Aqs IP\&. If the DNS server does not support DNS\-over\-TLS all DNS requests will fail\&.
243 .sp
244 When set to
245 "opportunistic"
246 DNS request are attempted to send encrypted with DNS\-over\-TLS\&. If the DNS server does not support TLS, DNS\-over\-TLS is disabled\&. Note that this mode makes DNS\-over\-TLS vulnerable to "downgrade" attacks, where an attacker might be able to trigger a downgrade to non\-encrypted mode by synthesizing a response that suggests DNS\-over\-TLS was not supported\&. If set to false, DNS lookups are send over UDP\&.
247 .sp
248 Note that DNS\-over\-TLS requires additional data to be send for setting up an encrypted connection, and thus results in a small DNS look\-up time penalty\&.
249 .sp
250 Note that in
251 "opportunistic"
252 mode the resolver is not capable of authenticating the server, so it is vulnerable to "man\-in\-the\-middle" attacks\&.
253 .sp
254 In addition to this global
255 \fIDNSOverTLS=\fR
256 setting
257 \fBsystemd-networkd.service\fR(8)
258 also maintains per\-link
259 \fIDNSOverTLS=\fR
260 settings\&. For system DNS servers (see above), only the global
261 \fIDNSOverTLS=\fR
262 setting is in effect\&. For per\-link DNS servers the per\-link setting is in effect, unless it is unset in which case the global setting is used instead\&.
263 .sp
264 Defaults to
265 "no"\&.
266 .sp
267 Added in version 239\&.
268 .RE
269 .PP
270 \fICache=\fR
271 .RS 4
272 Takes a boolean or
273 "no\-negative"
274 as argument\&. If
275 "yes"
276 (the default), resolving a domain name which already got queried earlier will return the previous result as long as it is still valid, and thus does not result in a new network request\&. Be aware that turning off caching comes at a performance penalty, which is particularly high when DNSSEC is used\&. If
277 "no\-negative", only positive answers are cached\&.
278 .sp
279 Note that caching is turned off by default for host\-local DNS servers\&. See
280 \fICacheFromLocalhost=\fR
281 for details\&.
282 .sp
283 Added in version 231\&.
284 .RE
285 .PP
286 \fICacheFromLocalhost=\fR
287 .RS 4
288 Takes a boolean as argument\&. If
289 "no"
290 (the default), and response cames from host\-local IP address (such as 127\&.0\&.0\&.1 or ::1), the result would not be cached in order to avoid potential duplicate local caching\&.
291 .sp
292 Added in version 248\&.
293 .RE
294 .PP
295 \fIDNSCacheSize=\fR, \fIMulticastDNSCacheSize=\fR, \fILLMNRCacheSize=\fR
296 .RS 4
297 Takes a non\-negative integer\&. Configures the maximum number of DNS resource record entries that may be stored in the per\-scope cache for unicast DNS, Multicast DNS (mDNS), and Link\-Local Multicast Name Resolution (LLMNR) respectively\&. Each defaults to 4096\&. The maximum allowed value is 16777216 (2^24)\&. Setting any of these to 0 effectively disables caching for the respective protocol\&. These settings are only effective when
298 \fICache=\fR
299 is set to
300 "yes"
301 or
302 "no\-negative"\&. If
303 \fICache=no\fR, caching is fully disabled regardless of these values\&.
304 .sp
305 Note that Multicast DNS relies heavily on caching for request suppression and efficient operation\&. It is recommended to keep
306 \fIMulticastDNSCacheSize=\fR
307 at a reasonably high value even when reducing
308 \fIDNSCacheSize=\fR\&.
309 .sp
310 Note that
311 \fBsystemd\-resolved\fR
312 automatically flushes all caches on system memory pressure, thus in most cases manual cache size configuration should not be necessary\&.
313 .sp
314 Note that caching is turned off by default for host\-local DNS servers\&. See
315 \fICacheFromLocalhost=\fR
316 for details\&.
317 .sp
318 Added in version 261\&.
319 .RE
320 .PP
321 \fIDNSStubListener=\fR
322 .RS 4
323 Takes a boolean argument or one of
324 "udp"
325 and
326 "tcp"\&. If
327 "udp", a DNS stub resolver will listen for UDP requests on addresses 127\&.0\&.0\&.53 and 127\&.0\&.0\&.54, port 53\&. If
328 "tcp", the stub will listen for TCP requests on the same addresses and port\&. If
329 "yes"
330 (the default), the stub listens for both UDP and TCP requests\&. If
331 "no", the stub listener is disabled\&.
332 .sp
333 The DNS stub resolver on 127\&.0\&.0\&.53 provides the full feature set of the local resolver, which includes offering LLMNR/MulticastDNS resolution\&. The DNS stub resolver on 127\&.0\&.0\&.54 provides a more limited resolver, that operates in "proxy" mode only, i\&.e\&. it will pass most DNS messages relatively unmodified to the current upstream DNS servers and back, but not try to process the messages locally, and hence does not validate DNSSEC, or offer up LLMNR/MulticastDNS\&. (It will translate to DNS\-over\-TLS communication if needed however\&.)
334 .sp
335 Note that the DNS stub listener is turned off implicitly when its listening address and port are already in use\&.
336 .sp
337 Added in version 232\&.
338 .RE
339 .PP
340 \fIRefuseRecordTypes=\fR
341 .RS 4
342 Takes a list of DNS record types separated by space\&. Specified record types in each query will be refused\&. This option can be specified multiple times\&. If an empty string is specified, then all previous assignments are cleared\&.
343 .sp
344 Examples:
345 .sp
346 .if n \{\
347 .RS 4
348 .\}
349 .nf
350 RefuseRecordTypes=AAAA SRV TXT
351 .fi
352 .if n \{\
353 .RE
354 .\}
355 .sp
356 Note that to refuse AAAA record (unlike SRV, TXT, etc\&.) completely, please also disable IPv6 stack in kernel with "sysctl \-w net\&.ipv6\&.conf\&.all\&.disable_ipv6=1"\&.
357 .sp
358 Added in version 258\&.
359 .RE
360 .PP
361 \fIDNSStubListenerExtra=\fR
362 .RS 4
363 Takes an IPv4 or IPv6 address to listen on\&. The address may be optionally prefixed with a protocol name ("udp"
364 or
365 "tcp") separated with
366 ":"\&. If the protocol is not specified, the service will listen on both UDP and TCP\&. It may be also optionally suffixed by a numeric port number with separator
367 ":"\&. When an IPv6 address is specified with a port number, then the address must be in the square brackets\&. If the port is not specified, then the service uses port 53\&. Note that this is independent of the primary DNS stub configured with
368 \fIDNSStubListener=\fR, and only configures
369 \fIadditional\fR
370 sockets to listen on\&. This option can be specified multiple times\&. If an empty string is assigned, then the all previous assignments are cleared\&. Defaults to unset\&.
371 .sp
372 Examples:
373 .sp
374 .if n \{\
375 .RS 4
376 .\}
377 .nf
378 DNSStubListenerExtra=192\&.168\&.10\&.10
379 DNSStubListenerExtra=2001:db8:0:f102::10
380 DNSStubListenerExtra=192\&.168\&.10\&.11:9953
381 DNSStubListenerExtra=[2001:db8:0:f102::11]:9953
382 DNSStubListenerExtra=tcp:192\&.168\&.10\&.12
383 DNSStubListenerExtra=udp:2001:db8:0:f102::12
384 DNSStubListenerExtra=tcp:192\&.168\&.10\&.13:9953
385 DNSStubListenerExtra=udp:[2001:db8:0:f102::13]:9953
386 .fi
387 .if n \{\
388 .RE
389 .\}
390 .sp
391 Added in version 247\&.
392 .RE
393 .PP
394 \fIReadEtcHosts=\fR
395 .RS 4
396 Takes a boolean argument\&. If
397 "yes"
398 (the default),
399 \fBsystemd\-resolved\fR
400 will read
401 /etc/hosts, and try to resolve hosts or addresses by using the entries in the file before sending query to DNS servers\&.
402 .sp
403 Added in version 240\&.
404 .RE
405 .PP
406 \fIReadStaticRecords=\fR
407 .RS 4
408 Takes a boolean argument\&. If
409 "yes"
410 (the default),
411 \fBsystemd\-resolved\fR
412 will read
413 /etc/systemd/resolve/static\&.d/*\&.rr,
414 /run/systemd/resolve/static\&.d/*\&.rr,
415 /usr/local/lib/systemd/resolve/static\&.d/*\&.rr,
416 /usr/lib/systemd/resolve/static\&.d/*\&.rr, and try to resolve lookups by using the entries in these files before sending query to DNS servers\&. This functionality is very similar to the one controlled by
417 \fIReadEtcHosts=\fR, but allows more flexible control of DNS resource records fields beyond just A/AAAA/PTR\&. See
418 \fBsystemd.rr\fR(5)
419 for details\&.
420 .sp
421 If both this option and
422 \fIReadEtcHosts=\fR
423 are enabled then this mechanism takes precedence: any records discovered via static resource records will take precedence over records under the same name from
424 /etc/hosts\&.
425 .sp
426 Added in version 261\&.
427 .RE
428 .PP
429 \fIResolveUnicastSingleLabel=\fR
430 .RS 4
431 Takes a boolean argument\&. When false (the default),
432 \fBsystemd\-resolved\fR
433 will not resolve A and AAAA queries for single\-label names over classic DNS\&. Note that such names may still be resolved if search domains are specified (see
434 \fIDomains=\fR
435 above), or using other mechanisms, in particular via LLMNR or from
436 /etc/hosts\&. When true, queries for single\-label names will be forwarded to global DNS servers even if no search domains are defined\&.
437 .sp
438 This option is provided for compatibility with configurations where
439 \fIpublic DNS servers are not used\fR\&. Forwarding single\-label names to servers not under your control is not standard\-conformant, see
440 \m[blue]\fBIAB Statement\fR\m[]\&\s-2\u[4]\d\s+2, and may create a privacy and security risk\&.
441 .sp
442 Added in version 246\&.
443 .RE
444 .PP
445 \fIStaleRetentionSec=\fR\fISECONDS\fR
446 .RS 4
447 Takes a duration value, which determines the length of time DNS resource records can be retained in the cache beyond their Time To Live (TTL)\&. This allows these records to be returned as stale records\&. By default, this value is set to zero, meaning that DNS resource records are not stored in the cache after their TTL expires\&.
448 .sp
449 This is useful when a DNS server failure occurs or becomes unreachable\&. In such cases,
450 \fBsystemd-resolved\fR(8)
451 continues to use the stale records to answer DNS queries, particularly when no valid response can be obtained from the upstream DNS servers\&. However, this does not apply to NXDOMAIN responses, as those are still perfectly valid responses\&. This feature enhances resilience against DNS infrastructure failures and outages\&.
452 .sp
453 \fBsystemd\-resolved\fR
454 always attempts to reach the upstream DNS servers first, before providing the client application with any stale data\&. If this feature is enabled, cache will not be flushed when changing servers\&.
455 .sp
456 Added in version 254\&.
457 .RE
458 .SH "SEE ALSO"
459 .PP
460 \fBsystemd\fR(1), \fBsystemd-resolved.service\fR(8), \fBsystemd-networkd.service\fR(8), \fBdnssec-trust-anchors.d\fR(5), \fBsystemd.rr\fR(5), \fBresolv.conf\fR(5)
461 .SH "NOTES"
462 .IP " 1." 4
463 ๐Ÿ’ฃ๐Ÿ’ฅ๐Ÿงจ๐Ÿ’ฅ๐Ÿ’ฅ๐Ÿ’ฃ Please note that those configuration files must be available at all times. If
464 /usr/local/
465 is a separate partition, it may not be available during early boot, and must not be used for configuration.
466 .IP " 2." 4
467 RFC 4795
468 .RS 4
469 \%https://tools.ietf.org/html/rfc4795
470 .RE
471 .IP " 3." 4
472 RFC 6762
473 .RS 4
474 \%https://tools.ietf.org/html/rfc6762
475 .RE
476 .IP " 4." 4
477 IAB Statement
478 .RS 4
479 \%https://www.iab.org/documents/correspondence-reports-documents/2013-2/iab-statement-dotless-domains-considered-harmful/
480 .RE