tgreenx
tgreenx
> Updated DNSSEC02 (#782) and created DNSSEC13 (#780) probably makes DNSSEC12 not needed any more. @matsduf So, to this day, should this issue be closed?
Solved by #1032 in release v2022.2.
Solved by #1005
@matsduf Closing this. Currently we are using Solution 1 as proposed in this PR, and this works fine for me too.
@matsduf I have updated this issue for the following: Basic00, Basic01, Basic02, Basic04, Connectivity04, DNSSEC02, Nameserver10, Nameserver15, Zone01, Zone09, Zone11.
Another issue I found with this Test Case: it outputs redundant messages because it loops over name servers and instantly outputs messages for each DNSKEY record found. Instead, the results...
> Another issue I found with this Test Case > [ ... ] @mattias-p @matsduf Should I create a separate issue for this? I'm not sure of the state of...
Hi @massimocandela, I think that the issue is not entirely resolved. After applying your fix, it seems that there are still connectivity issues in different places: File: _stdout_ ``` >...
Hi @massimocandela, Did you have some time to investigate this further? Thanks,
Indeed, this is a bug due to the fact that out of bailiwick lookups for fake delegations are being done in Zonemaster-LDNS rather than Engine, when `$fill_in_empty_oob_glue = 1`: https://github.com/zonemaster/zonemaster-engine/blob/v5.0.0/lib/Zonemaster/Engine.pm#L142