DynDNS client

Routers report their IP via DynDNS2 — but only when they notice the change themselves. The DynDNS client (dnseditor-dyndns-client) runs on a system that is on at the location anyway (server, NAS, container, Windows) and detects changes almost instantly: it holds one WebSocket connection per address family to the EE. When the public IP changes the connection dies — the reconnect carries the new source IP and the server applies it immediately. Without WebSocket (proxy/firewall) it automatically falls back to 60-second polling.

Setup in three steps

Create a target: on the project’s DynDNS page → New DynDNS target. The token is shown exactly once — together with the ready-made setup command.
Install the client (.deb/.rpm, Docker or as a Windows service) and run the command:
Terminal window
```
dnseditor-dyndns-client setup --host https://dns.example.com --token dnsedyn_…
```

Test and start:

dnseditor-dyndns-client update
sudo systemctl start dnseditor-dyndns-client

The DynDNS page then shows a green live dot per address family (v4/v6), the client version and the last IPs — dead clients stand out immediately.

IPv4 and IPv6

With the DynDNS service hostnames configured (admin area → core settings: A-only/AAAA-only) the client holds one connection per family — each reports itself. Without them it runs degraded: one connection via the main URL, the missing family taken from the local interfaces (public addresses only) and reported explicitly. dnseditor-dyndns-client status shows the active mode.

Behind a private CA: set ca_file in config.yaml. The token can only update the addresses of its one target; deleting the target voids it immediately.