Mats Dufberg
Mats Dufberg
Delegation05 needs to be rewritten so that there is clear specification of the message tags to be outputted by the implementation.
DNSSEC10 tests for the existence of NSEC and NSEC3 records by sending a query for a non-existing name. The [current specification] (and its implementation) does not correctly handle the case...
The test zone `dnssec13-algo-not-signed-dnskey.zft-root.rd.nic.fr` has DNSKEY records representing algorithms 5, 8 and 13. The DNSKEY RRset is mean to be signed by only one or two of these algorithms to...
In the implementation of [Nameserver08] ("Testing QNAME case insensitivity") and [Nameserver09] ("Testing QNAME case sensitivity") uses random query names, which prevents caching. [Nameserver08], but not [Nameserver09], requires the query name...
Nameserver11 checks for response on unknown EDNS option. However, it does not correctly verifies support for simple EDNS before testing support for the unknow option, which makes the outcome unclear:...
The format of the titles of the test cases varies much. Some are complete sentences, others are just short noun phrases. The titles can be seen in the [list of...
The test case depends that the subdomain "www" exists, or else it will only verify the RCODE. The implementation queries for the SOA record in "www" which will in most...
Where and when should the msgid for the messages be defined? They will be part of the code, that is not the issue, but should they be composed with the...
The DNSKEY RRset should be consistent over all name servers. Create a test case under consistency that verifies that. The multi-signer moder (https://datatracker.ietf.org/doc/html/rfc8901) challenges this requirement, so the level should...
Test cases Zone02-06 checks the SOA timer values, and emits messages when certain limits have been passed. Verify those limits against authoritative recommendations and review that correct [severity level] is...