All guides · Home server setup

Dynamic DNS for your home server and homelab

Keep a memorable address when your internet connection changes IP. uk.app dynamic DNS updates the A or AAAA record for your registered name, or a hostname beneath it, so you can use the same address for your server.

DDNS is included with annual registration: standard names cost £4.99 per year; new premium registrations cost £99.00 per year. Both include the same DNS features. Compare prices and renewal details.

What you need before enabling DDNS

Use an active, parked or grace-period uk.app name with managed DNS. Your router, NAS or server needs a client that supports a custom dyndns2 server over HTTPS. A built-in DDNS menu is not enough if it only supports a fixed provider list.

Check inbound connectivity first. Dynamic DNS does not bypass carrier-grade NAT, open firewall ports or provide hosting. For a website, configure a valid HTTPS certificate as well. The home server guide covers these separate steps.

1. Create a token for your name

Open My names → your name → Dynamic DNS and create a DDNS token. Copy it when shown and store it securely. This is the password for updates to that name, not your account password or a general REST API token. Replacing or revoking it stops clients using the old token.

2. Configure your client

Protocol

dyndns2, with HTTPS enabled

Server and path

ddns.uk.app and /nic/update

Username

Your full registered name, such as yourname.uk.app

Password

The DDNS token created for that name

Hostname to update

yourname.uk.app or a hostname beneath it, such as home.yourname.uk.app

These hostnames are examples; replace them with a name you control. Use the ddclient configuration and custom URL examples for your client. Protect any configuration file containing the token and avoid putting it in shared logs or screenshots.

3. Check the update result

An IPv4 update changes an A record; an IPv6 update changes an AAAA record. If the client omits myip, the endpoint uses the address of the request. A client running through a VPN or proxy may therefore report the wrong address for your home server. Updating one address family does not remove stale records from the other.

• good ip: the address was updated.
• nochg ip: the stored address already matches.
• badauth: check the registered name and token.
• nohost: check the hostname, registration status and managed DNS setting.

Check the resulting address with dig +short yourname.uk.app A or, in PowerShell, Resolve-DnsName yourname.uk.app -Type A. Repeat for AAAA if you use IPv6. Allow cached records to expire, then test the actual service from another network.

Use the same name for the service you run

For a web dashboard, follow the HTTPS certificate guide. For a game, configure the port using the Minecraft Java SRV guide. If DNS is correct but access still fails, use the connection troubleshooting steps.