A self-hosted Dynamic DNS solution similar to DynDNS or NO-IP.
You can use a hosted version at ddns.pboehm.de where you can register a
host under the d.pboehm.de domain (e.g test.d.pboehm.de).
Recent Changes
ddns has been fully restructured and now uses the PowerDNS
Remote Backend instead
of the Pipe Backend, which
is far easier to deploy. It now serves both the frontend and the backend over HTTP using different ports.
The old ddns source code can be found at the legacy tag.
Security Notice
Please make sure that you use the latest available version of ddns, as it contains an important security
fix for an issue introduced in the rework.
ddns is built around a small webservice, so that you can update your IP address simply by calling
an URL periodically through curl. Hosts that haven't been updated for 10 days will
be automatically removed. This can be configured in your own instance.
An API similar to DynDNS/NO-IP has not been implemented yet.
- A custom domain where the registrar allows setting
NSrecords for subdomains. This is important because not all DNS providers support this. - A server with docker and docker-compose installed
- The following ports should be opened in the firewall:
53/udp80/tcp443/tcp
For the domain you want to use with ddns (example.net in the following sections, please adjust this to your domain)
you have to create the following two DNS records:
ddns.example.netas aCNAMEorA/AAAArecord pointing to the serverddnswill be running on. This record will be used for accessing theddnsfrontend in your browser or viacurl. It is also the target for the correspondingNSrecord.d.example.netas anNSrecord pointing to the previously createdddns.example.netrecord. This will delegate all subdomains underd.example.netto the PowerDNS server running onddns.example.net.
The setup is now automated using docker-compose and only some customization has
to be made in a docker-compose.override.yml file
(a sample is available here).
The setup included in this repository contains all the components described above and uses caddy as a web server, because it provides automatic HTTPS using Lets Encrypt.
git clone git@github.com:pboehm/ddns.git
cd ddns/docker
cp docker-compose.override.yml.sample docker-compose.override.yml
Please adjust the settings in docker-compose.override.yml marked with the #<<< .... comments as follows:
- adjust the domain part in lines marked with
# <<< ADJUST DOMAINaccording to your DNS-Setup - insert your email address in lines marked with
# <<< INSERT EMAILwhich is required for getting certificates from Lets Encrypt
Finally execute the following docker-compose command, which creates 4 containers in detached mode which are also
started automatically after reboot. For updating an existing installation use the same command because it automatically
rebuilds the containers.
docker-compose --project-name ddns up -d --build