What's New

A host is now checked a second time before it counts as down. A single lost packet on the way to your host used to be enough to trigger a "Host down" email, and because the next check only runs after your chosen interval, the recovery mail then reported a full hour of downtime that never happened. Only a host that fails both checks is reported as down. Monitoring is also part of your activity log now: starting, pausing, resuming and stopping a check are recorded, as is every time a host goes down or comes back. The entries appear on the Activity page and on the zone or domain the host belongs to, so you can see the full history rather than just the last 24 checks.

The Dynamic DNS panel on the dashboard checked the wrong field for dynamic records on custom domains, so a record with a perfectly good IP address could show as "No IP set" and count against the active total. It now looks at the address the record actually serves.

Older MX records stored the priority as part of the mail server value, so the edit form showed something like "25 mail.example.com" in the Mail Server field with the wrong priority beside it. These records are now stored the same way as new ones, and the edit form shows the priority and mail server in their own fields.

DKIM generators and DNS tools often present long TXT values as several quoted parts. Pasting that format as-is could previously make the record fail to resolve. The parts are now joined automatically, so both plain and quoted formats work.

The text field for TXT records stopped accepting input at 255 characters, which silently cut off longer values such as DKIM keys. The field now accepts up to 4096 characters, and long values are automatically split into standard-length strings when published to DNS.

Long values such as DKIM keys squeezed the record tables into unreadable columns, especially on mobile. They are now shown collapsed to a few lines — tap or click a value to expand it. Records with special characters are also now always published to DNS in correctly sized strings.

Claiming a hostname that was imported from the old dyndns.dk and never linked to an account crashed with a server error after the update password was verified. The claim now completes and the hostname is added to your account as expected.

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.