Mats Dufberg
Mats Dufberg
> I meant that it could be checked that the ZONEMD digest (or other fields) is consistent across all name servers of the apex of a zone. Yes, and also...
Thank you for reporting this. I think your issue is about the same as #1174. We will take a look at the logic of [CONNECTIVITY04]. If you have your own...
Just be aware that profile.json in default path will be overwritten at update. The prefixes used by Zonemaster are the prefixes found in routing, not in the LIR table.
> Would it be sufficient to lower this WARNING to INFO if at least 1 NS exist on 2 different AS per protocol (IPv4 or IPv6)? Yes, I think that...
Thank you for the suggestions. SPF validation is already covered by [ZONE11] which is being implemented in https://github.com/zonemaster/zonemaster-engine/pull/1287 Test cases for DKIM och DMARC are planned. [ZONE11]: https://github.com/zonemaster/zonemaster/blob/master/docs/public/specifications/tests/Zone-TP/zone11.md
Comments on ZONE11 are of course welcome.
Will not be done.
Sending bad cookies is definitely part of the plan.
@tgreenx, no, the issue is not fully solved since there are still three different test cases that use the same message (NAMESERVER02, NAMESERVER12 and NAMESERVER13).
@pnax and @tgreenx, please re-review. I rebased and added minor fixes.