diff options
| author | Jorge Niedbalski <jnr@metaklass.org> | 2019-07-12 15:34:24 -0400 |
|---|---|---|
| committer | Jorge Niedbalski <jnr@metaklass.org> | 2019-07-17 10:42:53 -0400 |
| commit | 37d7a7d984ec7679711c2d31789f033f3b6dc2c2 (patch) | |
| tree | f4fb302ef3b0aa7d51e2e50e4ec4cc6444b53231 /man/resolved.conf.xml | |
| parent | 81c07a955590b44fe2b1f21780df353c0d8b62f6 (diff) | |
| download | systemd-37d7a7d984ec7679711c2d31789f033f3b6dc2c2.tar.gz | |
resolved: switch cache option to a tri-state option (systemd#5552).
Change the resolved.conf Cache option to a tri-state "no, no-negative, yes" values.
If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995),
however, there are several use cases on which this condition is not acceptable (See systemd#5552 comments)
and the only workaround would be to disable cache entirely or flush it , which isn't optimal.
This change adds the 'no-negative' option when set it avoids putting in cache
negative answers but still works the same heuristics for positive answers.
Signed-off-by: Jorge Niedbalski <jnr@metaklass.org>
Diffstat (limited to 'man/resolved.conf.xml')
| -rw-r--r-- | man/resolved.conf.xml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/man/resolved.conf.xml b/man/resolved.conf.xml index a647a4ace7..213be1d7b2 100644 --- a/man/resolved.conf.xml +++ b/man/resolved.conf.xml @@ -227,10 +227,11 @@ <varlistentry> <term><varname>Cache=</varname></term> - <listitem><para>Takes a boolean argument. If <literal>yes</literal> (the default), resolving a domain name + <listitem><para>Takes a boolean or <literal>no-negative</literal> as argument. If <literal>yes</literal> (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.</para> + If <literal>no-negative</literal>, only positive answers are cached. <para>Note that caching is turned off implicitly if the configured DNS server is on a host-local IP address (such as 127.0.0.1 or ::1), in order to avoid duplicate local caching.</para></listitem> |