DS03_ILLEGAL_ITERATION_VALUE should be WARNING and not ERROR (DNSSEC03)#1352
Merged
Conversation
matsduf
approved these changes
Feb 20, 2025
marc-vanderwal
approved these changes
Feb 24, 2025
marc-vanderwal
left a comment
Contributor
There was a problem hiding this comment.
I agree: if such a misconfiguration isn’t an immediate threat to the zone’s ability to be resolved, then ERROR is too harsh.
matsduf
added a commit
to matsduf/zonemaster-engine
that referenced
this pull request
May 12, 2025
Contributor
|
Implementation in zonemaster/zonemaster-engine/pull/1452 |
tgreenx
approved these changes
May 14, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Purpose
Even though RFC 9276 says "Validating resolvers MAY also return a SERVFAIL response when processing NSEC3 records with iterations larger than 0", we are not aware about any resolver that would be so strict at the moment. For now and apparently for not short time in the future non zero iterations will not cause immediate operational problem. Reporting non zero iterations as ERROR in DNS zone administration is too strict in this situation.
Context
https://datatracker.ietf.org/doc/html/rfc9276#name-recommendation-for-validati