Docs › Dynamic DNS

Dynamic DNS on Ubiquiti / UniFi

UniFi gateways send real HTTP Basic authentication, so the credentials stay in their own fields. The Server field differs between the UniFi OS gateways and the older USG line.

Where the setting lives

Settings ▸ Internet ▸ Dynamic DNS

Configuration

UniFi: Settings ▸ Internet ▸ Dynamic DNS

# UDM, UDM Pro, UXG and other UniFi OS gateways
Service:  custom
Hostname: nas.alice.home.network
Username: alice
Password: <your update password>
Server:   api.home.network/nic/update?hostname=%h&myip=%i

# USG and USG Pro, which use ddclient instead
Server:   api.home.network

Replace alice with your label and <your update password> with the password from the setup wizard. The username is your label, never your email address.

Worth knowing. Omit https:// from the Server field on either hardware. UniFi adds the scheme itself and a doubled scheme fails. On the USG line the Server field takes the bare hostname with no path and no variables, because ddclient builds the path itself. Leave Server empty when using one of the built-in providers rather than the custom one.

Check it worked

verify

# confirm the record moved
dig +short nas.alice.home.network @ns1.home.network

# the update endpoint answers with the dyndns2 status word
curl -u 'alice:<your update password>' \
  'https://api.home.network/nic/update?hostname=nas.alice.home.network&myip=auto'
good 203.0.113.7

good means the record changed, nochg means it was already correct. Both are success. badauth means the username or password is wrong, and 911 means the fault is at our end, so retry rather than reconfigure.

Still not resolving at home?

If the name answers from ns1.home.network but not from your own resolver, the resolver is stripping the private address as rebind protection. Fix it for your resolver.

← All documentation