What's New

A new guided wizard helps you set up SPF and DMARC records for your domain. It auto-detects your email provider from existing MX records (Google Workspace, Microsoft 365, Fastmail, One.com, IONOS, Hetzner, and more), pre-selects the right SPF includes, and generates correct TXT records with explanations at each step.

Common questions about dynamic hostnames, account access, and custom domains are now answered at kyedns.com/faq. Covers router DDNS setup, the dyndns.dk migration, IPv6 dual-stack, magic link login, and more.

Each account now has a personal API token (visible on your profile). Use it to read your zones, custom domains, and DNS records via a simple JSON API — handy for scripting and integrations.

Deleting a domain from KyedNS now goes through a confirmation page that runs a live nameserver lookup against public resolvers. If your registrar still points at KyedNS, deletion is blocked with an explanation — otherwise we would silently break DNS resolution for your domain. The domain details page also has a visible Delete button for the first time, so you don't have to hunt for it under Settings.

Set or change the destination URL for your Homepage Bookmark directly on the hostname page — no detour through Settings. The panel that shows the bookmark URL now has the destination field right next to it.

Revived the 2011 dyndns.dk WEBJUMP feature for free *.dyndns.dk hostnames. Set a URL like https://kyedns.com/go/yourhost.dyndns.dk as your browser homepage: every time the browser opens, your IP is updated and you're sent on to the destination you pick (e.g. google.com). No client to install, no router config, no scheduled tasks. Configure the redirect destination on the hostname page under Settings. The bookmark URL has no tokens — auth uses the 30-day sign-in session, so you'll re-authenticate roughly once a month. Useful if your router has no DDNS support and you just want something that works.

The legacy /opdat, /opdat.php, /update, /update/simple, and /pro/dynamic endpoints now return the standard DynDNS2 response vocabulary: "good {ip}" on a successful change, "nochg {ip}" when the submitted address matches what's on file, and the standard error codes "abuse", "badauth", "nohost", "notfqdn", "911". Previously they returned homegrown "OK: IP updated to ..." and "ERROR: ..." strings that some standards-compliant routers (e.g. D-Link DSR-250N) couldn't parse, causing them to retry successful updates indefinitely and trip the per-hostname rate limiter. If you have scripts or clients that grep for the old strings, update them to match the DynDNS2 codes. /api/v1/nic/update has always returned these codes and is unchanged.

DNS records on the domain page are now grouped by purpose (email delivery, email auth, AWS verification, TLS, DynDNS, website, other) with collapsible sections and an expand/collapse-all toolbar. The activity log is collapsed by default and fetches on demand, so the page loads faster. Submit buttons now show a visible "working…" state so a second click can't re-fire a request.

A regression in v1.14.0 caused edits to existing DNS records to redirect like normal but silently discard the change — renames, value updates, TTL changes, everything. Fixed. If you tried to edit a record in the last day and the change didn't stick, try again.

The propagation check page was marking every resolver as "Stale" even when the answers were correct. Blank expected-value fields are now ignored, and CNAME / MX / NS / SOA comparisons are case-insensitive and tolerate trailing-dot differences between dig and the built-in resolver.