DynDNS
Sign in
Dynamic DNS for UniFi and dyndns2 clients

Your IP address changes.
Your hostname keeps up.

When your internet provider hands your gateway a new public address, DynDNS updates the DNS record at your own provider within seconds. No third-party DDNS domain, no subscription, no cron scripts.

Sign in See how it works
  • Works with UniFi's built-in Dynamic DNS
  • IPv4 and IPv6
  • Your domain, your DNS provider
Your gatewayWAN address changed to 203.0.113.42
GET /nic/update
DynDNSChecks the credential and compares the address
good
PUT A record
Your DNS providerhome.example.com → 203.0.113.42
Works with UniFi Cloud Gateways inadyn ddclient routers with dyndns2 support curl

Everything a dynamic hostname needs, nothing it doesn't

A small service that does one job well, with a clear interface on top.

Updates only when needed

An unchanged address is answered from cache without touching your provider's API, so frequent check-ins cost nothing.

IPv4 and IPv6

A and AAAA records from a single request. Turn each one on or off per hostname.

A credential per device

Each gateway gets its own login, limited to the hostnames you choose. Revoke one without touching the rest.

See every update

An activity log records each request, its result and where it came from. Problems are obvious at a glance.

Guided gateway setup

Creating a credential shows exactly what to type into UniFi, with copy buttons for every field.

Pluggable providers

DNS providers are modules. Gandi LiveDNS is supported today, and more can be added.

Set up in three steps

About five minutes, most of it spent finding your API token.

  1. 1

    Connect your DNS provider

    Paste an API token. It's tested immediately and stored encrypted.

    Gandi LiveDNS
  2. 2

    Add your hostname

    Enter the name to keep updated, such as home.example.com. The zone is detected for you.

  3. 3

    Point your gateway at it

    In UniFi, add a custom Dynamic DNS entry with this server:

    ddns.example.com/nic/update?hostname=%h&myip=%i

Self-hosted, and careful with your keys

DynDNS runs on your own server. Your DNS provider credentials never leave it.

  • Encrypted provider tokensAPI tokens are encrypted at rest and never shown again after you save them.
  • Hashed passwordsSign-in and device passwords are stored only as argon2 hashes.
  • Scoped accessEach device credential can update only the hostnames it's been granted.
  • Rate limitedRepeated failed sign-ins and excessive update requests are throttled.

Ready to keep your hostname in sync?

Sign in to connect a provider and set up your first hostname. Accounts are created by your administrator.

Sign in