Skip to content

Keep your Cloudflare A record up to date with DDNS Updater

How-toDeployrr v6.0+CurrentDomain and DNSRemote accessDocker

Most home internet plans give you a public IP that changes now and then. When it does, your Cloudflare A record points at the old address and your apps stop opening from outside. DDNS Updater checks your public IP and fixes the A record for you. This page shows how to install it and how to set it up the way Deployrr expects.

  • It checks your public IP every 12 hours and updates the record in Cloudflare when the IP has changed. After an update it waits 5 minutes before it will update again.
  • It updates only the root record of your domain (@), for IPv4 only. The record’s TTL is 600 seconds.
  • It has a web page at http://SERVER_IP:PORT. If the Deployrr Dashboard runs, it also has an entry there.
  • It keeps its own backups every 96 hours in appdata/ddns-updater/backups.

This is about your public IP, the address the internet sees. It is not your server’s LAN address. For that, see Change the server IP.

  • You have a Basic, Plus or Pro license. A Free license can’t install official apps. You see a License Required box. See Licenses.
  • You finished Prerequisites. See the Quick start.
  • You use Cloudflare for your domain, and the A record for your root domain already exists. See DNS records Deployrr expects.
  • You know your Cloudflare Zone ID. In Cloudflare, select your domain and open the Overview tab to find it. See Find your Zone ID. To change the token later, see Change or rotate the token.
  • You have a Cloudflare DNS API token. DDNS Updater reuses the one you typed in Proxy > Traefik > Preparation. That step needs a Plus or Pro license, Hybrid setup mode and Socket Proxy running. See Set up Traefik. If you can’t run it, make a token by hand. See If the token is empty.
  1. Go to Apps > Browse Apps.
  2. Select DDNS Updater (“Dynamic DNS updater”).
  3. Choose Install.
  4. At “Do you want to install this app?”, choose Yes.
  5. In the Port Configuration box, accept the suggested port (8000, or the next free one) or type another.
  6. In the Required Information box, paste your Cloudflare Zone ID from the Overview tab. The box shows what you type.
  7. If Traefik is running, Deployrr asks more questions. See If Traefik is running.

Don’t cancel the Required Information box. The install still finishes, but the Zone ID stays blank. If that happens, fill in zone_identifier in config.json by hand. See Edit config.json.

Deployrr sets up the app with your Domain 1 as the domain.

The install doesn’t warn you if the token is empty. After the install, open config.json and check the "token" line. See If the token is empty.

Deployrr asks for these in order:

  1. Traefik Subdomain. It suggests ddnsupdater.
  2. A login method for the app.
  3. In Advanced mode only, an exposure method: Both, Internal or External.

You edit appdata/ddns-updater/config.json in the next two sections. The steps are the same each time.

  1. Go to your Docker folder. The cdd command comes from the Deployrr bash aliases. Without the aliases, use cd with the full path of your Docker folder.

    Terminal window
    cdd
  2. Back up the config file:

    Terminal window
    cp appdata/ddns-updater/config.json appdata/ddns-updater/config.json.bak
  3. Open the file:

    Terminal window
    sudo nano appdata/ddns-updater/config.json
  4. Make your change, then save the file.

  5. Restart the app:

    Terminal window
    sudo docker restart ddns-updater

If the file has a typo, copy the .bak file back over it and restart again.

The config Deployrr writes has "proxied": true. DDNS Updater then turns the root A record orange (proxied) in Cloudflare. Domain Checks wants the record gray (DNS only). See Fix orange cloud records. To see why a proxied record fails the checks, watch Deployrr 5 walkthrough: Domain Checks and gray-cloud records at 41:44 (shows Deployrr v5; menus and steps differ in v6).

If you follow the gray-cloud setup, change that setting to false.

  1. Follow the steps in Edit config.json.

  2. In step 4, find the line "proxied": true, and change it to:

    "proxied": false,

Deployrr copies the token from the Traefik Preparation step into the config. If you never ran that step, the "token" value in config.json is empty and DDNS Updater can’t change your record.

  1. In Cloudflare, go to My Profile > API Tokens. Make a user token, not an Account API token. Give it these two permissions:

    • Zone / Zone / Read
    • Zone / DNS / Edit

    See Fix the Cloudflare token for more.

  2. Follow the steps in Edit config.json.

  3. In step 4, put the token between the quotes of the "token" line.

Every reinstall writes a fresh config.json. You lose "proxied": false and any token or Zone ID you added by hand. Do the edits again. Keep your .bak copy so you can compare. An app update with a new image leaves the file alone. See Restart, Recreate or Reinstall.

  1. Go to Apps > Browse Apps. The DDNS Updater line shows [Running]. [Installed] means it is installed but not running. See Install and manage apps from the Apps menu.

  2. Open http://SERVER_IP:8000 in a browser. Replace SERVER_IP with your server’s LAN IP, and 8000 with your port if you changed it.

  3. Read the log:

    Terminal window
    sudo docker logs ddns-updater

    With the Deployrr bash aliases: dlogs ddns-updater. Press Ctrl+C to stop following the log.

  4. In Cloudflare, open DNS > Records. The A record shows your current public IP, and the cloud is gray if you set "proxied": false.

DDNS Updater only updates the root record. Deployrr’s setup uses a wildcard CNAME (*) that points to your root domain, so your subdomains follow the root record.

If you made the wildcard an A record with an IP instead, it will not be updated. Change it to a CNAME that points to your root domain. See DNS records Deployrr expects. To see the root A record and wildcard CNAME made by hand, watch Traefik 3 guide: Cloudflare settings at 7:35 (manual Docker Compose setup).

A dynamic DNS updater can’t help if your ISP puts many customers behind one shared public IP (CG-NAT). Port forwards on your router then do nothing. For how to check and what to do, see Behind CG-NAT. For the options in v6, watch Deployrr 6 overview: Options for CG-NAT at 4:37. For background on how CG-NAT breaks port forwarding, read UDMS part 18: CG-NAT (manual setup).

  • The web page does not open. Check that the app is running and that you used the right port. If another app uses the port, see Port already in use.
  • The log shows an error from Cloudflare. Check the Zone ID, the domain and the token in config.json. The token needs Zone / Zone / Read and Zone / DNS / Edit.
  • The record is still orange. Set "proxied": false as shown above and restart the app.
  • Your IP changed and the record is old. The app checks every 12 hours, so the record can stay old for a while. Read the log to see when it last checked.