zonemd generation doesn't cause flushing zone to disk

In case of non-signed zone when zonemd-generate is enabled, zone file on disk is not flushed after adding zonemd. I'd expect zone to be flushed to disk like signed zones.

zonefile-load: "difference" is only setting, everything else is defaults.

I guess this happens just once, when you turn on ZONEMD generation in zonefile?

If so, it's already documented as a minor limitation https://www.knot-dns.cz/docs/3.1/singlehtml/index.html#zonemd-generate

I assume that, the next time the ZONEMD is updated iff the zone is updated otherwise, which shall cause zonefile flush by itself. Could you please confirm?

Won't happen if I edit zone multiple times. zonefile won't get flushed to disk if it's not signed. DDNS causes flushing to disk but ZONEMD doesn't. Also notice there is no other way to force ZONEMD generation than editing zone when zone is not signed.

Did more experiments.

knotc zone-flush zone.tld. +outdir /var/lib/knot

Now there is ZONEMD record which is correct.

edited zone so that serial changes.

After that zone on disk has same old ZONEMD record.

So ZONEMD calculation should cause automatic writing of zonefile when configuration has default setting for zonefile-sync.

This seems really weird. The (live, queriable) SOA changed, while ZONEMD remained unchanged (and thus no longer valid)? Could you first focus on the correctness of those records (SOA, ZONEMD), that are answered by Knot when queried (e.g. by kdig), and after that, compare it to what is (not) being written back to zonefile?

Sorry for possible misunderstanding, but you are a bit too brief for me to get the whole picture..

Zone query and secondaries have correct zone data. Problem is only that when ZONEMD is updated zone is not flushed to disk.

If commanded with knotc to flush zone to disk, correct data is written to disk.

So now unsigned zone behaves like you'd have zonefile-sync: -1 in config. Updating ZONEMD should trigger syncing zone to disk.

Also verified zone-backup writes correct zone.

OK, thank you.

I have found a hopefully fixing bugfix, but please be patient, I need to make sure it doesn't damage any specific use-case.

mentioned in merge request !1358 (merged)

mentioned in commit 1a49c679

closed with merge request !1358 (merged)