Skip to content
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

Modify the "Notice" information when DNSSEC not signed #193

Closed
sandoche2k opened this issue Mar 22, 2016 · 2 comments
Closed

Modify the "Notice" information when DNSSEC not signed #193

sandoche2k opened this issue Mar 22, 2016 · 2 comments
Assignees
Labels
P-High Priority: Issue to be solved before other T-Bug Type: Bug in software or error in test case description

Comments

@sandoche2k
Copy link
Contributor

For DNSSEC tests, first check whether DS and DNSKEY are available. If both are not available, then issue a "NOTICE" saying "The domain is not signed with DNSSEC"

@sandoche2k sandoche2k added T-Bug Type: Bug in software or error in test case description P-High Priority: Issue to be solved before other Stability labels Mar 22, 2016
@sandoche2k sandoche2k added this to the Release 2016.1 milestone Mar 22, 2016
@pawal
Copy link
Contributor

pawal commented Mar 23, 2016

This is dnssec07, which could probably be run first of all DNSSEC tests. If no DNSKEY or DS exists, no other DNSSEC tests at the DNSSEC level are relevant.

@sandoche2k
Copy link
Contributor Author

@vlevigneron "Shouldn't the message below be "The domain is not signed with DNSSEC" rather than "There are neither DS nor DNSKEY records for the zone". This is just a query. For me, either messages are OK.

zonemaster-cli motounit.fr
Seconds Level Message
======= ========= =======
25.21 WARNING All nameservers IPv4 addresses are in the same AS (16276).
25.21 WARNING All nameservers IPv6 addresses are in the same AS (16276).
25.21 WARNING All nameservers are in the same AS (16276).
25.28 NOTICE There are neither DS nor DNSKEY records for the zone.
27.54 NOTICE SOA 'refresh' value (10800) is less than the recommended one (14400).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P-High Priority: Issue to be solved before other T-Bug Type: Bug in software or error in test case description
Projects
None yet
Development

No branches or pull requests

3 participants