What's New

A webhook delivery that hits a server error or timeout is now retried a few times instead of being dropped, so a short restart of your endpoint no longer loses events. And a failing webhook is no longer disabled permanently after three failures: it is paused with a growing cooldown, you get an email about it, and the first successful delivery resets everything — no manual re-enabling needed.

Records that can be monitored now show an Uptime monitoring panel on their edit page — pick a port and start monitoring without leaving the record. The same panel appears on a free hostname's settings page, shows the current status once a monitor exists, and lets you pause or remove it. Monitored records also get a status pill in the domain's records list.

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 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.

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.

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.

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.

When you add a dynamic DNS record, the IP field is now prefilled with the address you are connecting from, so the hostname resolves right away instead of pointing nowhere until your first update. You can still change or clear it if the client that keeps the record updated runs on a different machine.

Records that a domain inherits from a template used to show as a read-only "Inherited" row with nothing you could do to them. Your templates are yours too, so each inherited record now has an "Edit in template" button that takes you straight to it. Editing there updates every domain that uses the template.