Skip to content

Conversation

@frankarinnet
Copy link
Contributor

Associated issue: #334

Its a few lines of changes to "Zone.addRecord()" that allow for ingesting zones that have both a SOA and an associated RRSig/SOA.

Additionally, there's a test case that demonstrates the bug (fails on 3.6.1, works if the fix is applied).

@ibauersachs
Copy link
Member

Thanks a lot for noticing and coming up with a PR!

Did you also test if replacing a signed SOA still works? I wonder if the remembering only the SOA record alone (instead of its rrset) is even working in that case.

If the license allows it, we could maybe import the sample zone file.

@frankarinnet
Copy link
Contributor Author

re: replacing signed SOAs: I created a second test case for that. It seemed to work, but you should look at it carefully. I'm not 100% sure it addresses your question.

re: the sample zone file: it was just the one I was able to find browsing google. You'd have to ask them ("The DNS Institute") about licensing. The properly-signed examples I have access to are all reverse-related and anyway have our own contacts all over them.

@ibauersachs ibauersachs merged commit 6e1786e into dnsjava:master Sep 8, 2024
@ibauersachs ibauersachs added this to the v3.6.2 milestone Jan 26, 2025
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