Docs › Dynamic DNS

Dynamic DNS on Synology

DSM lets you add a provider of your own. Add one entry under Customize Service Provider, then select it when creating the DDNS record.

Where the setting lives

Control Panel ▸ External Access ▸ DDNS ▸ Customize Service Provider

Configuration

Synology: Customize Service Provider

Service Provider: home.network
Query URL:        https://__USERNAME__:__PASSWORD__@api.home.network/nic/update?hostname=__HOSTNAME__&myip=__MYIP__

Then create the DDNS entry:
  Hostname: nas.alice.home.network
  Username: alice
  Password: <your update password>

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. DSM substitutes the four tokens into the Query URL and sends no separate authentication header, so the credentials have to appear in the URL as shown. Filling only the Username and Password boxes produces a silent badauth. The tokens are case sensitive and doubly underscored: __USERNAME__, __PASSWORD__, __HOSTNAME__, __MYIP__. The Query URL also rejects spaces and semicolons, and each provider entry carries one hostname.

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