filiparag / hetzner_ddns

Hetzner Dynamic DNS (DDNS, DynDNS) daemon

Hetzner Dynamic DNS Daemon

A simple daemon to continuously update Hetzner DNS A and AAAA records for your server with a dynamic IP address.

It features support for multiple subdomain records with painless configuration and administration.

Installation

Prebuilt packages

Officially supported operating systems:

• Alpine Linux
• Arch Linux (AUR)
• Debian / Ubuntu
• Docker (Docker Hub)
• Fedora / openSUSE (Copr)
• FreeBSD (Ports tree)
• NetBSD

Packages for the latest stable version can be found here.

Feel free to contribute to first-party support for other operating systems.

Manual Installation

Dependencies: awk, curl, jq.

# Download
git clone https://github.com/filiparag/hetzner_ddns.git
cd hetzner_ddns

# Install
sudo make install

# systemd service
sudo make systemd

# FreeBSD service
sudo make freebsd-rc

# NetBSD service
sudo make netbsd-rc

# OpenRC service
sudo make openrc

Configuration

Configuration file is located at /usr/local/etc/hetzner_ddns.conf

# Seconds between updates / TTL value
interval='60'

# Hetzner DNS API key
key='18fe3b02339b23ef2418f9feda1b69ef'

# Top level domain name
domain='example.com'

# Space separated host subdomains (@ for domain itself)
records='homelab media vpn'

To obtain an API key, go to Hetzner DNS Console.

Configuration for prebuilt packages

Default configuration location differs in prebuilt packages:

• Linux distributions: /etc/hetzner_ddns.conf
• FreeBSD: /usr/local/etc/hetzner_ddns.conf
• NetBSD: /usr/pkg/etc/hetzner_ddns.conf

Manage records for multiple domains

Currently, this utility supports management of one domain per daemon. If you have multiple domains, use CNAME records to point them to one the daemon will manage, as shown in the following example:

# Managed domain (master.tld)
@		IN	A	    1.2.3.4
@		IN	AAAA	1:2:3:4::

# Other domain
service		IN	CNAME	master.tld.

Multiple daemon instances for systemd

If your operating system relies on systemd, you can easily run multiple daemons as shown below:

# Create configuration file for foobar.tld domain
sudo cp -p /usr/local/etc/hetzner_ddns.conf.sample /usr/local/etc/hetzner_ddns.foobar.conf

# Modify created file to reflect your preferences

# Enable and start foobar.tld's daemon
sudo systemctl enable hetzner_ddns@foobar

Usage

Run on startup

# systemd
sudo systemctl enable hetzner_ddns

# FreeBSD and NetBSD
sudo service hetzner_ddns enable

# OpenRC
sudo rc-update add hetzner_ddns

Start/Stop

# systemd
sudo systemctl start/stop hetzner_ddns

# FreeBSD, NetBSD and OpenRC
sudo service hetzner_ddns start/stop

Log file is located at /var/log/hetzner_ddns.log

hetzner_ddns's Issues

Package repos are not containing 0.2.3

I just checked copr and it's still showing 0.2.2-1.fc34 from 1y 5m ago. Seems other repos are also outdated.

Service is not starting and config file is not being found on my installation

Hi!

I'm trying to get your application working inside a libvirt's VM, the OS I'm using is Alpine 3.18.2.

I have installed the package via apk but I can´t figure out what I'm doing wrong...

I'm getting this errors:

localhost:/# hetzner_ddns
jq: error (at <stdin>:0): Cannot iterate over null (null)

localhost:/# service hetzner enable
 * service: service `hetzner_ddns' does not exist
localhost:/etc# 

localhost:/# hetzner_ddns start
unable to read configuration file

Any clue?

Thank you very much for sharing this @filiparag !!

Copr repodata folder missing (at least on Fedora 39)

Hi, when trying to update I get the following error:

Copr repo for hetzner_ddns owned by filiparag                                                                                     321  B/s | 341  B     00:01    
Errors during downloading metadata for repository 'copr:copr.fedorainfracloud.org:filiparag:hetzner_ddns':
  - Status code: 404 for https://download.copr.fedorainfracloud.org/results/filiparag/hetzner_ddns/fedora-39-x86_64/repodata/repomd.xml (IP: 13.225.78.78)
Error: Failed to download metadata for repo 'copr:copr.fedorainfracloud.org:filiparag:hetzner_ddns': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

There is indeed no repodata folder at that address: https://download.copr.fedorainfracloud.org/results/filiparag/hetzner_ddns/fedora-39-x86_64/

Can you have a look please?

Docker - IPv6 only via network_mode host

Thank you for the application! Please add that the IPv6 AAAA records are only updated when docker is running in network_mode host :)

Use ip.hetzner.com instead of Akamai

Hi,

maybe it"s a goog idea to retrieve IP from Hetzner instead of Akamai. This would remove dependency to a third party:
curl -4 https://ip.hetzner.com and curl -6 https://ip.hetzner.com

See also https://ip.hetzner.com/

Alpine Linux: run supervised and not as root

Hi,

I think it's a good idea to run supervised and not as root in Alpine Linux.

Wildcard subdomains unexpeted expansion

Couldn't quite figure out where it happens but the wildcard subdomain seems to be receiving a shell expanseion somewhere.

Placed "@ *" into records variable. Debian 11.2

[2022-11-16 15:30:29] Missing both records for bin.example.org
[2022-11-16 15:30:29] Missing both records for boot.example.org
[2022-11-16 15:30:30] Missing both records for dev.example.org
...

It seems that the asterisk is being expanded to the files in the root directory somewhere, but I couldn't figure it out- the obvious contenders are taken care of (no missing double quotes i could find...)

With --daemon argument config file cannot be found

Hi,

when started with daemon argument, the config file cannot be found because it wants to open /usr/local/etc/hetzner_ddns.--daemon.conf.

Problem installing on Raspberry Pi

Hello,
thanks for the code, that's exactly what I'm looking for! Sorry, I'm kind of a n00b here. I sucessfully installed it on one Raspberry Pi, but on the other one I get the following error:

Job for hetzner_ddns.service failed because the control process exited with error code.
See "systemctl status hetzner_ddns.service" and "journalctl -xe" for details.

where status yields:

● hetzner_ddns.service - Hetzner Dynamic DNS
     Loaded: loaded (/etc/systemd/system/hetzner_ddns.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Sat 2024-02-10 11:55:00 CET; 5s ago
       Docs: man:hetzner_ddns(1)
    Process: 17068 ExecStartPre=/usr/bin/touch /var/log/hetzner_ddns.log (code=exited, status=0/SUCCESS)
    Process: 17069 ExecStartPre=/usr/bin/chown daemon:root /var/log/hetzner_ddns.log (code=exited, status=203/EXEC)`

and journalctl:
`Feb 10 11:56:32 openpihole systemd[17123]: hetzner_ddns.service: Failed at step EXEC spawning /usr/bin/chown: No such file or>
░░ Subject: Process /usr/bin/chown could not be executed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The process /usr/bin/chown could not be executed and failed.
░░
░░ The error number returned by this process is ERRNO.
Feb 10 11:56:32 openpihole systemd[1]: hetzner_ddns.service: Control process exited, code=exited, status=203/EXEC
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStartPre= process belonging to unit hetzner_ddns.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 203.
Feb 10 11:56:32 openpihole systemd[1]: hetzner_ddns.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit hetzner_ddns.service has entered the 'failed' state with result 'exit-code'.
Feb 10 11:56:32 openpihole systemd[1]: Failed to start Hetzner Dynamic DNS.
░░ Subject: A start job for unit hetzner_ddns.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit hetzner_ddns.service has finished with a failure.
░░
░░ The job identifier is 1018797 and the job result is failed.

Do you have any idea on how to solve this? Thanks!