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.

TXT record values now accept a DKIM key copied straight from your mail server's key file or a dig answer — including the record name, parentheses, quoted line chunks, and trailing comment. We unwrap the formatting and store the key itself, so a blind copy-paste just works. Previously the quotes could survive into the record and break DKIM validation.

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 propagation checker now takes record names the same way the record forms do: enter _dmarc or mail._domainkey and it is checked under your domain automatically. Long record values in tables also hint that a click expands them.

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.

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.

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.

Records that come from a template are now copied into the domain that uses it, so the domain page lists everything the zone actually serves in one place. They are marked as coming from a template and are edited on the template itself, which keeps every domain using it in step, and the row links straight there. Removing a template from a domain now leaves its records behind as that domain's own, so detaching can never quietly empty a live zone; delete any you no longer want. If your domain already has a record identical to one in the template, it is reused rather than duplicated, and records that differ are kept side by side, so per-domain verification records, like the ones Apple and Google issue, are safe. One thing to know: a template cannot replace a record you already have with a different value. If you are pointing several domains at one server, delete the old record first, then attach the template.