Implements a dynamic DNS service for Hetzner's Domain Registration Robot.
Developed for the FRITZ!Box 7362 SL.
- gpg (command line tool)
- openssl (required by the SMTP library)
dyndns-daemon reads its configuration from the environment. Necessary entries are:
| Name | Description | Type |
|---|---|---|
| FROM_ADDR | "From" address as used in the email to the robot. | String |
| TO_ADDR | Address of the robot. (robot@robot.first-ns.de) | String |
| SMTP_HOST | Hostname of the SMTP server, including port | String |
| SMTP_USERNAME | Username for the SMTP service | String |
| SMTP_PASSWORD | Password for thr SMTP service | String |
| PGP_KEY | ID of the GPG Key that will be used for signing the email | String |
| DOMAIN | Domain that will be managed | String |
| HETZNER_USER | Hetzner username | String |
| SERVER_ADDR | Address on which will be listened for HTTP requests | String |
| HTTP_AUTH_USER | Username for HTTP authentication for incoming requests. | String |
| HTTP_AUTH_PASSWORD | Password for HTTP authentication for incoming requests. | String |
| IP_RESOLV_METHOD | String | |
| IP_HEADER | Name of the header which contains the IP address of the true client. | String |
| TEMPLATE | File containing a template for the generated zonefile. | String |
See also the exmaple .env file.
There are two ways of detecting the IP Adress of the client.
If you define IP_RESOLV_METHOD as Header the server will take the IP from the header definied in IP_HEADER.
If you define IP_RESOLV_METHOD as DynDns2 the server will work with the specific dyndns function of most homeuse routers. In this case the IP_HEADER value will be ignored.
To generate a zonefile for the managed domain, dyndns-daemon uses a template, where {%SERIAL%} is replaced by a 64-bit timestamp and {%IP%} is
replaced by the client ip respectively.
@ IN SOA ns1.first-ns.de. postmaster.robot.first-ns.de. (
{%SERIAL%}; Serial
86400; Refresh
7200; Retry
604800; Expire
7200); Minimum
@ IN NS ns1.first-ns.de.
@ IN NS ns.second-ns.de.
@ IN A {%IP%}
See also the example file.
- The GPG key used for signing the email content must not be protected with a password. This is due to gpg refusing to accept the password as an argument and creating a prompt..