Adding a zone by a different name than its apex causes "hung" status

[ximon18]

# cat /tmp/arya.zone
$ORIGIN cascade.nlnetlabs.nl.
$TTL 240
@       IN  SOA rusty.nlnetlabs.nl. hostmaster.nlnetlabs.nl. 3 28800 7200 604800 240

@       IN  NS  rusty.nlnetlabs.nl.
@       IN  TXT "Stichting NLnet Labs Cascade DNSSEC signer zone"

; rusty public interface
@       IN  A   185.49.141.18
; @     IN  AAAA 2a04:b900:0:100::18

# ./cascade zone add --source /tmp/arya.zone --policy arya example.com
Added zone example.com

# ./cascade zone status example.com
Status report for zone 'example.com' using policy 'arya'
✔ Waited for a new version of the example.com zone
✔ Loaded <serial number not yet known>
  Loaded at 2025-10-07T11:42:22+00:00 (24s ago)
  Loaded 292 B and 4 records from the filesystem in 0 seconds

And that's as far as it gets. In the log I see:

[ZL]: Zone file '/tmp/arya.zone' lacks a SOA record. Skipping zone.

This should not appear hung, and the error should be shown to the user.

[ximon18]

On latest main the behaviour has changed slightly in that the log now no longer mentions skipping of the zone but instead says:

2026-02-16T12:31:45.758285Z ERROR cascaded::loader: Could not reload Name(example.com.): the zonefile could not be loaded: the zonefile has the wrong origin name

The zone status output is still the same, but one could now argue it is more wrong than it was before:

✦ ❯ target/release/cascade --server 127.0.0.1:2006 zone status example.com
Status report for zone 'example.com' using policy 'default'
✔ Waited for a new version of the example.com zone
✔ Loaded <serial number not yet known>
  Loaded at 2026-02-16T13:33:37 (1m 51s ago)
  Loaded 1378 MB and 0 records from the filesystem in 0 seconds

Here we see a tick mark against "Loaded" yet in the log there is an error that the zonefile could NOT be loaded.