DynDNS client

The DynDNS client (dnseditor-dyndns-client) runs on a system that is on at the location anyway (server, NAS, container, Windows) and keeps its DynDNS target in the cloud current — IPv4 and IPv6. Instead of polling it holds one WebSocket connection per address family: when the public IP changes the connection dies, the reconnect carries the new source IP and the cloud applies it immediately. Without WebSocket (proxy/firewall) it automatically falls back to 60-second polling.

Included in all plans — Free too; the held channel actually reduces platform load compared to polling.

Setup

Create a DynDNS target on the project’s DynDNS page — the token is shown exactly once, with the ready-made setup command.
Install the client (.deb/.rpm, Docker or as a Windows service) and run the command — without --host it talks to the dnseditor.de cloud automatically:
Terminal window
```
dnseditor-dyndns-client setup --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 (via the region’s v4/v6 service hostnames), the client version and the last IPs. Routers (FRITZ!Box etc.) keep using the DynDNS2 endpoint — the client complements them for systems that run anyway.