What's New
Stay up to date with the latest KyedNS features and improvements
June 2026
Use internationalized names for domains, hostnames, and records
June 18, 2026You can now create and view domains, free DynDNS hostnames, and DNS records using their native script — Danish characters like ø, å and æ, German ones like ä, ö, ü and ß, or any internationalized name. Type the readable form and it just works; we still store and serve the canonical "xn--" form for DNS, and show it on hover.
May 2026
Fleet heartbeat monitor
May 13, 2026A new Fleet section lets you monitor your dynamic DNS hosts with active TCP probing — configurable port, 5-minute check interval, and email alerts when a host goes down or recovers. Each host shows a 24-probe sparkline so you can spot patterns at a glance. Free accounts can monitor up to 4 hosts.
Fleet monitor auto-pauses on stale host
May 13, 2026The fleet monitor now automatically pauses probing when a dynamic host goes stale — so you won't get false down-alerts if the IP has moved. Monitoring resumes automatically on the next valid DynDNS update.
SPF & DMARC email security wizard
May 02, 2026A 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.
April 2026
FAQ page
April 24, 2026Common 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.
Read-only API for zones, domains, and DNS records
April 22, 2026Each 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.
Safer domain deletion — live nameserver check
April 21, 2026Deleting 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.
Homepage Bookmark destination now editable on the hostname page
April 21, 2026Set 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.
Homepage Bookmark: set as browser homepage, IP updates on every open
April 20, 2026Revived 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.
Legacy DynDNS endpoints now return standard DynDNS2 response codes
April 20, 2026The 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.