-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add TTL support? #31
Comments
Thanks for proposing this. Would you tell us a bit about the design you have in mind to add the feature? |
Thanks for looking at it. I've looked over it a little. The underlying TTL can be stored in this record when retrieved. Cache reads can then verify liveness and only return if the entry is live. That happens here so an expired entry would trigger a standard query to DNS again. I'd make it optional so when it's disabled you're not storing TTLs unnecessarily. |
Will definitely look at a PR. If you can share your use case, that will help us with context, too. Thanks! |
Wonderful. |
Made a submission #32 to start this off. |
I'm evaluating this for possible use in another project. It seems to be the nicest resolver available, but I need something with an expiring cache that respects TTL.
Would the team consider a PR to support TTL?
The text was updated successfully, but these errors were encountered: