-
Notifications
You must be signed in to change notification settings - Fork 33
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.
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
DNSSEC16 test case implementation #900
DNSSEC16 test case implementation #900
Conversation
@matsduf The messages are not yet fully implemented but this test case can already be tested. |
@matsduf implementation "finished" (no translation yet). We have to add new unit tests when we will find broken zone or when we will be able to configure these broken zone. |
@matsduf Can you have a look ? I will not add more unit tests (only one message tage is not covered for the moment, I made some modification on Bind to prevent some checks that allow to load broken zones). I start to work on dnssec17. If we can merge dnssec16 before, it will be easier for the merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will do some "live" tests too.
@matsduf Can you test again with dnssec16-delete-cds.zft-root.rd.nic.fr broken zone ? I do not understand why you have not the DS16_DELETE_CDS message tag. |
|
@matsduf that's because you should add "--level info" to see this kind (INFO) of message tag. |
Correct. Missed that. |
Release testing for v2021.1Works as expected. |
Updated 2021-05-17:
How to test this PR
Read the test case specification for DNSSEC16 and verify that the implementation correctly reports issues and non-issues on selected zones to cover as many message tags as possible.