Back to Changelog
Panel Backend
v1.0.441
A DNS zone a migration broke can now be repaired from the panel
Bug Fixes
8- A zone that cannot be loaded no longer refuses every edit. Until now the rule was "the zone must be valid after your change", and a zone that arrived from cPanel with more than one conflict could not be taken apart at all: no single deletion made it valid, so every deletion was refused. The rule is now "your change must not add a new problem", so a broken zone can be cleaned up one record at a time while a healthy zone still cannot be broken.
- The DNS screen says what is wrong in plain words — which name holds both an alias and its own records, which placeholder was never filled in — instead of quoting the zone parser. Problems that have exactly one sensible resolution can be fixed with one click; the rest are described and left alone.
- A zone that is beyond picking apart can be rebuilt from the default template. It is destructive, it says so, and nothing triggers it automatically.
- Records deleted while a zone is unloadable no longer come back on the next restart. The published file is deliberately left in place (an unloadable file would take the domain off the air) and the panel now says the file is behind the records instead of silently disagreeing with itself.
- The two writers that created the conflict in the first place were corrected: creating a subdomain over an existing alias, and importing a cPanel zone on top of the panel template. The rule itself now lives on the record model, so no code path — including ones not written yet — can store a name that is both an alias and an address.
- Migration keeps address records it used to discard: a host that pointed at the old server follows the site here, a host that points at another provider is imported unchanged. Multi-line DKIM keys, TTLs written as 1h/30m/1d and TXT values longer than a single DNS string are all handled instead of being dropped.
- New: a diagnostic report for a zone (records, the published file, both validator verdicts, and the nameserver log) that can be downloaded and attached to a support ticket without giving anyone SSH access.
- BIND ownership of its own cache and runtime directories is restored at startup, so a restore or a file copy no longer leaves the nameserver unable to write (SH-072).