AXFRDDNS: Ignore ZONEMD records #3551
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ZONEMD records are DNSSEC-like, so we'll handle them like the other DNSSEC records and simply ignore them. See https://datatracker.ietf.org/doc/html/rfc8976 for more information.
|
CC @hnrgrgr |
|
Thanks for fixing that! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ZONEMDrecords are DNSSEC-like, so we'll handle them like the other DNSSEC records and simply ignore them. See https://datatracker.ietf.org/doc/html/rfc8976 for more information.I've enabled
ZONEMDgeneration on the zone used in theAXFRDDNS_DNSSECintegration test server, so any other PRs are likely to fail until this is merged. I have not enabled it on theAXFRDDNS(no DNSSEC) zone, so any failures there should be unrelated to this PR.