Self-host DDNS Updater with Levelrail
Keeps DNS records pointed at your changing public IP for many providers, with a small web page showing each record's status. The install form carries config.json as an editable file, so you add your providers there.
- Authorqdm12
- LicenceMIT
- Memory32 MiB
- Services1
How to self-host DDNS Updater
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/qdm12/ddns-updater:v2.10.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8000.
-
Fill in the secrets
2 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- The starter config has no providers. Edit the config.json setting, add one entry per record using the provider guides in the project docs, and reinstall or update to apply it.
DDNS Updater requirements
- Memory
- About 32 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then DDNS Updater. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the DDNS Updater docs page.
Deploy DDNS Updater your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy DDNS Updater from the CLI
levelrail-cli templates install ddns-updater --name my-ddns-updater Deploy DDNS Updater with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/ddns-updater/install \
-d '{
"name": "my-ddns-updater"
}' DDNS Updater configuration
DDNS Updater services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| ddns-updater | ghcr.io/qdm12/ddns-updater:v2.10.0 | 8000 | data -> /updater/data |
DDNS Updater environment variables
| Variable | Service | Value |
|---|---|---|
| CONFIG_FILEPATH | ddns-updater | Preset by the template |
| DATADIR | ddns-updater | Preset by the template |
Ports and volumes
- Ports
- 8000
- Volumes
- 1 named mount: data -> /updater/data
DDNS Updater FAQ
How much memory does DDNS Updater need?
The catalog lists about 32 MiB of memory for DDNS Updater.
Does DDNS Updater run on arm64?
For DDNS Updater, arm64 support is not confirmed; amd64 is unknown.
What licence is DDNS Updater under?
DDNS Updater is licensed under MIT, which is permissive, with few conditions on reuse.
Does DDNS Updater need configuration before it starts?
No. The template fills in its own defaults.
Which ports does DDNS Updater use?
DDNS Updater listens on port 8000 inside the stack.
Where does DDNS Updater keep its data?
In a named volume: data mounted at /updater/data.
Can I deploy DDNS Updater on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for DDNS Updater, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/qdm12/ddns-updater:v2.10.0 is what you deploy there.