Choose what should stay reachable
Use a hostname you manage, such as home.example.com. uDDNS will keep that
name pointed at your changing public address.
Multi-provider dynamic DNS
Keep DNS pointed at the address you actually have.
uDDNS checks your public IPv4 and IPv6 addresses, compares them with saved state, and updates your provider only when an address changes.
Latest release v3.0.1- 01Findyour public address
- 02Comparewith the last check
- 03Change DNSonly when needed
- 04Rememberthe new address
Before setup
Bring three things
You do not need to understand DNS internals, but you do need control of a hostname and a computer that can keep uDDNS running.
Create the narrowest credential
Use a token or key that can edit only the DNS records uDDNS needs. Your provider’s guide explains which values to copy.
Pick where it will run
A home server, NAS, or small computer works well. It must reach the internet and remain on when your public address changes.
Provider coverage
One runtime, several DNS APIs
Choose the company that manages your hostname. Advanced setups can use several accounts or a backup provider, with details kept in the repository.
- Cloudflare
- DuckDNS
- No-IP
- Dynu
- Namecheap
- Route 53
- Porkbun
- Hetzner
- DigitalOcean
- Gandi
- Linode
- OVH
- bunny.net
- Contabo
- DynDNS-compatible
Choose a home
Match uDDNS to what you already run
There is no single best installation. Pick the option that fits the computer you already maintain.
Already use containers?
Choose Docker Compose. It keeps uDDNS and its saved address in a small, isolated service.
Maintain a Linux server?
Choose systemd. The operating system can start uDDNS after a reboot and record its messages.
Trying it for the first time?
Run it directly while you configure and preview the first check. Move it into a background service after it works.
Daily use
Most checks should do nothing
That is the normal result. uDDNS contacts your provider only after it sees a new public address.
-
No change
Your saved address still matches. uDDNS leaves the DNS record alone and checks again later.
-
Updated
Your public address changed and the provider accepted the new record.
-
Failed
The record may still point to the old address. Read the named error, then check the provider credential and hostname.
-
Keep credentials private
Do not paste configuration or debug logs into an issue until you have checked them for account details.
Optional deeper look
Follow an address from discovery to DNS
The interactive map shows how uDDNS checks an address, decides whether anything changed, contacts the selected provider, and records the result.