The recursor cache needs to check stale when updating the ns type cache. #14117
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
When an NS record already exists in the recursor cache and the NS record is replaced again, the TTD setting of the NS record should check the stale flag of CacheEntry. Otherwise, the TTL of the NS cache will always be s_serveStaleExtensionPeriod(30s). Then the new NS cache will expires quickly, causing delays in iterative DNS resolution
Checklist
I have: