Hetzner DDNS

Hetzner DDNS is a lightweight Docker container that automatically updates the DNS records for your domain in the Hetzner DNS console whenever your public IP…

  • Network Services
  • Tools & Utilities
Hetzner DDNS is a lightweight Docker container that automatically updates the DNS records for your domain in the Hetzner DNS console whenever your public IP changes, keeping self-hosted services reachable behind a dynamic connection.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

47/100 Fair

Maintained
38last commit 350 days ago
Popular
2928 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
100no serious findings, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 41 days ago

GitHub stars
28
Open issues
8
Last commit
2025-12-06
Latest release
2.1
License
MIT
Activity
stale

Checked 18 days ago - source: GitHub (kutzilla/docker-hetzner-ddns)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Add your Hetzner API token first Before starting the app, put your Hetzner API token in the token/API setting so requests can send it as a Bearer token (the secure proof it's you). Without a valid token, Hetzner rejects the requests and DNS updates won't happen. source
  • Test the token with a simple read Do a quick test by reading the servers endpoint with a simple GET request (a safe “show me” request) before you rely on the app. If that test fails, the token or project access is wrong and the app will not work either. source
  • Send changes with a POST request When the app makes a change, the request should include your Bearer token and a JSON payload (the small package of details being sent). If the format or authorization is missing, Hetzner may refuse the change and your DNS record won't update. source
  • Quick setup Set ZONE_NAME to the domain zone to update and API_TOKEN to the API token created in the Hetzner DNS console. source

Fetched 38 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which environment variables are required to run the container?

Set ZONE_NAME to the Hetzner DNS zone, API_TOKEN to your Hetzner API token, and RECORD_TYPE to A for IPv4 or AAAA for IPv6.

How do I update multiple DNS records?

Use the RECORD_NAME_ pattern, for example RECORD_NAME_VPN=vpn and RECORD_NAME_WEBSITE=www. The plain RECORD_NAME value is ignored when multiple records are defined.

Can I set a different TTL for each record?

Set RECORD_NAME_<record>_TTL for each record, such as RECORD_NAME_VPN_TTL=600. If no per-record TTL is set, the default is 86400, and the generic TTL argument is ignored when per-record TTLs are used.

How often does it check the public IP and DNS record?

It uses CRON_EXPRESSION for the update interval, defaulting to every 5 minutes.

How do I make it start automatically after a reboot?

Run the container with --restart=always so it restarts automatically after the host reboots.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads