ddns-updater v0.1.0

Networking

DDNS Updater — keeps your dynamic-DNS records pointed at your current public IP across many providers (Cloudflare, Namecheap, DuckDNS, and dozens more), with a small web dashboard. Deployed as a single host-networked Nomad service.

nomad-pack run ddns-updater --registry nomploy

…or one line (add registry + run)

curl -fsSL https://packs.nomploy.com/install.sh | sh -s -- ddns-updater

Needs nomad-pack on PATH. The script only adds the nomploy registry and runs this pack.

Source ↗ Project ↗ ★ 3.2k ⚑ Report an issue

2 tasks http 8000 1 volume image qmcgaw/ddns-updater:latest tracks :latest image bumped today

Variables 9

values.hcl

Save as values.hcl, edit, then run:

nomad-pack run ddns-updater -f values.hcl --registry nomploy

# The name of the Nomad job.
job_name = "ddns-updater"

# The Nomad namespace to deploy into.
namespace = "default"

# The datacenters to deploy to.
datacenters = ["*"]

# The DDNS Updater container image. Pin a tag in production.
image = "qmcgaw/ddns-updater:latest"

# Host port for the DDNS Updater web UI.
port = 8000

# Named volume mounted at /updater/data (holds config.json and the update history).
data_volume = "ddns_updater_data"

# Optional inline JSON config (the CONFIG env), e.g. {"settings":[{"provider":"cloudflare","domain":"example.com",...}]}. Takes precedence over /updater/data/config.json. Leave empty to instead edit config.json in the data volume.
config_json = ""

# Placement constraints. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
constraints = []

# The task resources.
resources = {
    cpu    = 300
    memory = 256
  }

Name	Type	Default	Description
job_name	string	"ddns-updater"	The name of the Nomad job.
namespace	string	"default"	The Nomad namespace to deploy into.
datacenters	list	["*"]	The datacenters to deploy to.
image	string	"qmcgaw/ddns-updater:latest"	The DDNS Updater container image. Pin a tag in production.
port	number	8000	Host port for the DDNS Updater web UI.
data_volume	string	"ddns_updater_data"	Named volume mounted at /updater/data (holds config.json and the update history).
config_json	string	""	Optional inline JSON config (the CONFIG env), e.g. {"settings":[{"provider":"cloudflare","domain":"example.com",...}]}. Takes precedence over /updater/data/config.json. Leave empty to instead edit config.json in the data volume.
constraints	list	[]	Placement constraints. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
resources	object	{ cpu = 300 memory = 256 }	The task resources.

Back up this pack

This pack stores data in one Docker named volume: ddns_updater_data

restic

# Run on the node hosting this pack. Point restic at your repo first:
#   export RESTIC_REPOSITORY="s3:https://<account>.r2.cloudflarestorage.com/<bucket>"
#   export RESTIC_PASSWORD="<repo-password>"
#   export AWS_ACCESS_KEY_ID=<key>  AWS_SECRET_ACCESS_KEY=<secret>
restic backup \
  /var/lib/docker/volumes/ddns_updater_data/_data

rclone (sync to S3/R2)

rclone sync /var/lib/docker/volumes/ddns_updater_data/_data backup:<bucket>/ddns_updater_data

Paths assume the default Docker volume location (/var/lib/docker/volumes). Restore by stopping the job, restoring files into the same volume, and re-running the pack.

Readme

ddns-updater

DDNS Updater — keeps your dynamic-DNS records pointed at your current public IP. It supports dozens of providers (Cloudflare, Namecheap, DuckDNS, DigitalOcean, Gandi, deSEC, and many more), checks your IP on a schedule, updates records only when they change, and shows status + history in a small web dashboard.

Single host-networked Nomad service with a persistent data volume.

Deploy

nomad-pack registry add nomploy https://github.com/Nomploy/nomad-packs
nomad-pack run ddns-updater --registry=nomploy

Configure

Variable	Default	Description
`port`	`8000`	Web UI port (`LISTENING_ADDRESS`).
`config_json`	`""`	Optional inline JSON config (`CONFIG` env). Takes precedence over the file. See below.
`image`	`qmcgaw/ddns-updater:latest`	Container image. Pin a tag in production.
`data_volume`	`ddns_updater_data`	`/updater/data` — `config.json` and update history.
`resources`	`{ cpu = 300, memory = 256 }`	Task resources.

You must add your records. Two ways: set config_json to your provider config (recommended for GitOps), e.g. {"settings":[{"provider":"cloudflare","zone_identifier":"...","domain":"example.com","host":"@","ttl":300,"token":"..."}]}, or leave it empty and edit config.json in the data volume (the pack seeds an empty {"settings":[]}). See the provider docs for the exact fields. A prestart init task chowns the volume to uid 1000.