Skip to content

ISSUE-316 Fix caching for CNAME and DNAME#320

Closed
dropofwill wants to merge 1 commit into
dnsjava:masterfrom
dropofwill:ISSUE-316
Closed

ISSUE-316 Fix caching for CNAME and DNAME#320
dropofwill wants to merge 1 commit into
dnsjava:masterfrom
dropofwill:ISSUE-316

Conversation

@dropofwill
Copy link
Copy Markdown

This is a WIP for #316 , I tried to come up with a test, but don't know the internals well enough atm to do so yet. I did manually test for my use case and it does seem to be caching responses, but haven't verified TTLs are handled to spec.

This is a WIP, I tried to come up with a test, but don't know the
internals well enough atm to do so. I did manually test for my use case
and it does seem to be caching responses, but haven't verified TTLs are
handled to spec.
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Apr 1, 2024

@ibauersachs
Copy link
Copy Markdown
Member

Hi, sorry for not reacting earlier and thanks for your effort.
While fixing security issues, I had to refactor parts of LookupSession, which now should include caching of xNAME responses. I'm closing this PR for now. Please let me know if you still encounter issues with v3.6.0, we can then reopen this PR if required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants