Comment 5 for bug 1668771
Revision history for this message
| Jorge Niedbalski (niedbalski) wrote Re: systemd-resolved negative caching for extended period of time | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
5c191ba
demo site
(Get the code!)
I've made a proposal to change the resolved.conf Cache option to a tri-state "no, no-negative, yes" values. [0]
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 #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.
[0] https:/