Back to Changelog
Panel Backend
v1.0.436
Fixed DNS record deletion falsely reporting an error while actually deleting the record, which locked the affected zone from further edits.
New Features
2- Added a startup self-heal that restores DNS records which were already lost to this bug (still present in the zone file on disk but missing from the database) before any other zone-regenerating self-heal runs.
- Users are now warned when attempting to delete the last remaining nameserver record for a domain, asking them to add a replacement nameserver first.
Improvements
3- Zone file generation is now validated with named-checkzone before being written in all code paths (subdomain creation, migration import, and self-heal routines), not just the main DNS record editor.
- Zone validation fails open (with a warning logged) when the named-checkzone tool itself is missing on the host, so DNS edits are not blocked server-wide on installations without BIND validation tools; it still fails closed when the zone content itself is invalid.
- Rejected DNS edits no longer leave behind timestamped zone backup files.
Bug Fixes
2- DNS record deletion no longer removes the record from the database before validating the resulting zone file; a failed validation now leaves the record intact instead of silently deleting it while reporting an error to the user.
- Fixed a bug where a zone whose database state had already drifted from disk became permanently unable to accept any further DNS edits, since every subsequent change hit the same validation failure.