April 2nd, 2026
New
Improved
Fixed
It has been a little quiet here the last couple of months, but for a very good reason!
We have been hard at work implementing some major new features. Their foundation has been laid and the first versions are now live!
Besides these new features, we've also deployed various fixes and improvements since the last changelog.
The first new feature allows us to fully migrate zones between provider accounts. Migrations are possible to zones of the same provider as well as to other provider types, and even to different zones*.
Migrations are fully configurable, meaning that when migrating a zone, you can configure which components you would like to migrate. So far we've implemented support for migrating the records and access (users and profiles with whom the zone is shared). In the future we can expand this by implementing support for pending or scheduled mutations, for example.
Migrations are also infinitely repeatable, meaning they can be run again (with the same or different components).
This feature is only available internally to us for the time being. Please contact our Support Department if you would like to utilize ctrlDNS for your zone migrations.
*=Provided that only compatible components are migrated.
The next major feature is an all-new validation engine for zones. With this engine we can detect any kind of issues with the zone, such as differing TTLs for a Resource Record Set or a lack of nameserver records.
This powerful feature gives us a lot of possibilities in validating and auditing DNS zones and we’re planning on expanding this very soon.
In addition to, and to work in tandem with, the validation engine, we have reworked how synchronization errors are handled. Errors will now be reported to the zone log, giving you the tools and feedback necessary to resolve these errors yourself.
Our goal is still to prevent as many validation related errors as possible by reporting these early via either inline validation (i.e. in the various forms) or with the new zone validation engine. But for the cases we've not yet handled, we now fallback to reporting them as-is.
The per-account zone collection view did not correctly update the amount of zones count when creating zones via ctrlDNS
Fix the menu not properly decrementing the invite and mutation counters when deleting zones
Fixed the locale not respecting your preferences on error pages
Fixed an issue where deleted zones at Cloudflare did not correctly propagate
Fix Error 500 when changing the record type form field from TXT to SPF with an existing TXT record with invalid SPF data
Fix the password reset form not being submissible
Fix an issue that occurred when running the zone discovery process for Cloudflare accounts without any zones
Work around Realtime Register validation inconsistency between their UI and API, causing certain changes to not be synchronizable
Improved the error message when performing an action that results in a non-unique CNAME record
Improved the CAA record validation
Dropped support for Vimexx as they no longer have an API
Further harden the validation to ensure Realtime Register domain names are always in lower case
Nicely handle the insufficient permission Exonet API error when attempting to delete a zone
Nicely handle the Realtime Register API error when attempting to delete a zone that is managed
Nicely handle the Cloudflare API error when attempting to add a zone when the zone limit has been reached
Nicely handle the Realtime Register API error when attempting to create a zone that already exists
Improve the experience for adding an Openprovider account by validating if API access is enabled