Skip to content

Add comments why the first test should/could have a different result. #8

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add comments why the first test should/could have a different result. #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions sets/resolver/val_nsec3_optout_ad.rpl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -233,6 +233,16 @@ ENTRY_END

; recursion happens here.
; no AD flag on this because an optout NSEC3 is used.
; It could be argued that the right answer is SERVFAIL. The reason is that
; an NSEC3 opt-out range can only contain insecure delegations. Any
; name with authoritative data has to have its own NSEC3 entry. So we can
; conclude that example.com does not have any authoritative data for
; sub.example.com. It is possible that sub.example.com is an insecure
; delegation. However, in that case the resolver should have returned a SOA
; record with sub.example.com as the owner, and should have left out the
; NSEC3 records.
; Note that the tests as is (NOERROR/NODATA) is what validating resolvers
; return in practice.
STEP 10 CHECK_ANSWER
ENTRY_BEGIN
MATCH all
Expand Down