-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat: honor cache flush #201
Conversation
I've had issues with embedded devices changing IP's and appearing with both the previous and current IP. I'm guessing this goes for other records too? |
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.
Thanks for your PR! Please see comments inline. And could you please add tests for the new feature?
Thanks for the response, I'll dive into it 👍 |
I had some trouble constructing a proper test. My idea was to start browsing, similar to the test |
Broke a test putting into draft while looking at it. |
Lines 2775 to 2784 in 1b9647d
And a different, possible simpler approach is to construct a |
I fixed the already existing test. Thanks for the help with understanding, I'll attempt writing a specific cache-flush test now. |
Test added for cache flush - hope it's ok. |
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.
Thanks for your updates. Some minor comments inline.
Thanks for the feedback, I've stoppede squashing the commit, if you prefer me to, let me know. |
According to RFC 6762, when the cache-flush bit is set on a RR, all previously cache entries should be set to expire 1 second in the future if the RR created more than 1 second ago. This bit was previously called 'UNIQUE` which might have the same meaning, but cache-flush seems more in line with the RFC
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, thanks !
According to RFC 6762, when the cache-flush bit is set on a RR, all previously cache entries should be set to expire 1 second in the future.
This bit was previously called 'UNIQUE` which might have the same meaning, but cache-flush seems more in line with the RFC