What's New

Deleting a record template that domains still use is now refused, and the message names the domains so you know where to detach it first. Before, the template vanished while its records stayed live in DNS with nothing marked as pending. Attaching or removing a template now marks the domain as having pending changes, so the deploy page reflects that the served records will change. The Email Security panel now also recognises SPF and DMARC records that come from a template: a protected domain is shown as protected, with a note saying the records come from a template. Those records are edited on the template itself, so a second conflicting copy cannot be added by mistake.

Renaming a template marked every domain using it as having pending changes, but the deploy page then found nothing to deploy and offered no way to clear it. The deploy page now has a Force Republish button that publishes the zone again under a new serial number and clears the pending state, without changing any records. It replaces Clear Pending Flag, which only covered some of the ways a domain could get stuck.

Accounts created since April were missing their API token, so the token was blank on Account Settings and API requests came back unauthorized. Every account now has a token, and new accounts get one at signup.

When a domain is transferred or a hostname is claimed by a new account, the new owner now sees activity from their own tenure only. The previous owner's history, including their address updates, stays with them. Activity links were also fixed so every entry leads to a page you can actually open.

A hostname that dropped out of our nameservers only came back if its IP address happened to change. If your address stayed the same, your update client kept checking in normally and the dashboard looked fine, but the name never started resolving again. Check-ins now restore a missing hostname on their own, whether the address changed or not. Mail records on free hostnames are also kept intact when a domain is deployed, and a hostname that was switched off no longer comes back online on the next deploy.

Adding a domain now deploys it to our nameservers right away, so registries that check the new nameservers before accepting a change (such as punktum.dk for .dk domains) approve the switch on the first try. Previously the domain only went live after a manual deploy, and a nameserver change requested before that was rejected. Record edits are still staged until you deploy them, as before. We also now catch typos in the domain ending when a domain is added, instead of accepting names that can never resolve.

If we temporarily disable a hostname on our side, the update service now answers your router or update client with a retryable error instead of a code that makes well-behaved clients stop permanently. Once the hostname is re-enabled, updates resume on their own with no reconfiguration needed. Rate-limited hostnames still get the hard stop, so misconfigured clients back off.

On iPhone and iPad, tapping a delete button (or any other action that asks for confirmation) could leave the button spinning forever without ever showing the confirmation prompt. This happened after navigating back to a page, and only a reload would fix it. The culprit was a Safari quirk that silently blocks the browser's built-in prompts after a back swipe. Confirmations now appear as a regular dialog on the page itself, which is immune to the quirk, and the button spinner no longer starts until you have confirmed. As a bonus, cancelling a confirmation no longer leaves a stuck spinner on any platform.

Entries in your personal activity feed (RSS) now use the same friendly event names as the dashboard, such as "DNS Synced", instead of raw internal event codes. Failed DNS syncs also no longer show technical error details in the feed or on the activity page.

The email security wizard now has a "this domain's own mail server" option and keeps everything your SPF record already authorized. Before, picking a provider (e.g. Google or Hetzner) would overwrite the whole record and quietly drop the entry for a mail server you host yourself, which could start sending your outgoing mail to spam. The wizard now preserves those entries and pre-selects your own server when it sees one.