tgreenx

> @tgreenx, are you fine with this? Could you implement it? We should wait for test zones specification (and data) first, so I propose to postpone to v2024.1.

> Unfortunately, it will not be possible to check that the signature is valid. I meant that it could be checked that the ZONEMD digest (or other fields) is consistent...

@matsduf What is the status of this issue? Today, using Engine v4.7.2 (release v2023.1.3): ``` $ zonemaster-cli --no-ipv6 --show-testcase --level INFO welcometoparadi.se Seconds Level Testcase Message ======= ======== ============== =======...

@mattias-p @matsduf Does the template ([Template01](https://github.com/zonemaster/zonemaster/blob/v2023.1.3/docs/internal/templates/specifications/tests/Template01.md)) sound like a reasonable solution? It was added by https://github.com/zonemaster/zonemaster/pull/971 in v2021.2. I believe this issue can be closed.

Solved by https://github.com/zonemaster/zonemaster-engine/pull/762

> @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). From my understanding of...

@mattias-p I think this can be closed. In recent releases, on Debian 11, I had no issue creating a zip file when doing the release testing.

@mattias-p We have https://github.com/zonemaster/zonemaster/blob/v2023.1.3/docs/public/specifications/tests/MasterTestPlan.md#glossary, but it needs to be enriched. Maybe a proper document is more appropriate.

> Perhaps it should also warn if all name servers are in a single IPv4 /24 or IPv6 /48. Hi, This was added in v2022.2, with a new Test Case:...

Solved by #882