dnsdist: Add the ability to cap the TTL of records after insertion into the cache #12384
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rgacogne
force-pushed
the
ddist-cap-ttl
branch
from
8cdab9c to
c1791a5
Compare
rgacogne
added a commit
to rgacogne/pdns
that referenced
this pull request
Jan 13, 2023
Needs PowerDNS#12384 and the rebase PR.
rgacogne
added a commit
to rgacogne/pdns
that referenced
this pull request
Jan 13, 2023
Needs PowerDNS#12384 and the rebase PR.
chbruyand
approved these changes
Jan 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Short description
This pull request introduces the ability to cap the TTL of records after they have been inserted into the packet cache, so that we can keep them in cache for as long as possible but still return a lower TTL to the client.
Note that this pull request builds on #12383 and will have to be rebased.Checklist
I have: