-
Notifications
You must be signed in to change notification settings - Fork 31.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dns: restore dns query cache ttl #57640
dns: restore dns query cache ttl #57640
Conversation
Review requested:
|
Fixes: nodejs#57636 Co-authored-by: Robert Nagy <[email protected]>
da48077
to
61f93c1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Can you open the follow-up issue to track that work?
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #57640 +/- ##
==========================================
- Coverage 90.22% 90.22% -0.01%
==========================================
Files 630 630
Lines 185055 185056 +1
Branches 36216 36218 +2
==========================================
- Hits 166975 166963 -12
- Misses 11042 11047 +5
- Partials 7038 7046 +8
🚀 New features to boost your workflow:
|
Landed in b85505d |
I'm assuming this will land cleanly and removed the |
Fixes: nodejs#57636 Co-authored-by: Robert Nagy <[email protected]> PR-URL: nodejs#57640 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]>
Fixes: #57636
When c-ares was updated the default caching behavior changed.
This PR restores the caching behavior by setting
qcache_max_ttl
to0
.This change in c-ares is reasonable; thus, as a follow up to this fix, we should implement a cache management API for DNS queries and then re-enable the new default cache value. Tracking issue for follow up work: #57641