What's New

A CNAME or MX target without a dot, e.g. "www" or "mail", now means a host in the same domain, as in a standard zone file. In a template, the target becomes a host in each domain that uses the template. Before, such a target pointed nowhere. Targets with a dot, e.g. "mail.example.com", are unchanged.

You can add a "null MX" record: type MX, priority 0 and a single dot as the mail server. It tells other mail servers at once that the domain takes no mail. Before, the dot was refused as an invalid hostname.

When the DS record at your registrar does not match your domain's DNSSEC key, for example after a typo in the key tag, the domain page now says so and shows both key tags. Before, it showed misleading warnings about your nameservers and MX records.

You can now type a full name such as www.example.com in a record's Name field on example.com. It is saved as www, and example.com itself is saved as @. Before, the domain was added a second time, so the record went live as www.example.com.example.com.

The record_change and sync_fail webhook events could be selected but were never sent. Now record_change arrives when a record on one of your domains is created, changed or deleted, and sync_fail arrives when publishing a domain to our DNS servers fails. Update tokens and record notes are never included.

Each account can now create up to 3 free hostnames per hour, on the dashboard or through an AI assistant. This stops automated sign-ups from grabbing names in bulk. Hostnames you already have are not affected.

Changing or clearing a hostname address on its settings page, or through an AI assistant, now fires the ip_change webhook and shows up in the hostname activity, just like an update from your router. When an address is cleared, new_ip is null.

KyedNS now speaks the Model Context Protocol, the standard that lets AI assistants like Claude use external services. Point your assistant at kyedns.com/mcp with the API token from your account settings, and it can add, edit and deploy the DNS records on your domains, check monitoring, and look after your hostnames, all in plain language. A few things stay in the dashboard for now: DNSSEC, record templates, webhooks and monitors, and adding or deleting a domain. Every change made this way is marked in your activity log, and account settings now has a button to regenerate your API token, which instantly cuts off any client using the old one. Because tokens could previously only read your account and can now also make changes, every existing API token has been replaced as a precaution: if you use the API, grab your new token from account settings. Setup details are on the API page.

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.