What the Community DDNS Setup Was Trying to Do
The community post shared a config.json example for the ddns-updater application using DuckDNS. The key idea is still valid: the updater needs a provider, domain, credential or token, and an IP-version policy, and the persistent configuration must be stored where the container can read it after restart.
For a current ZimaOS-oriented overview, see the DuckDNS hardware and setup guide and the current ZimaOS App Store requirements directory.
Use the Current ddns-updater Schema
The upstream project documents provider-specific configuration, so do not blindly copy an old example when the provider schema may have changed. The current DuckDNS documentation requires a DuckDNS domain and token and supports IP-version options. The authoritative reference is the ddns-updater DuckDNS documentation. The main project README also documents supported providers and persistent configuration behavior in ddns-updater project documentation.
{
"settings": [
{
"provider": "duckdns",
"domain": "your-name.duckdns.org",
"token": "YOUR_TOKEN",
"ip_version": "ipv4"
}
]
}Replace the placeholders with your own values and never publish the real token in screenshots, forum posts, Git repositories, or support tickets.
Where to Find the Configuration on ZimaOS
The original thread referred to an appdata/ddns-updater path, but the exact host path can depend on how the app was installed and how its storage was mapped. Instead of assuming one fixed path, open the app settings in ZimaOS and identify the persistent volume mapped to the container's configuration location. Back up the current file before editing it.
How to Validate the Update
- Confirm the container starts without a JSON parsing error.
- Check the updater logs for provider authentication or domain errors.
- Resolve the hostname from another network or public DNS resolver.
- Compare the returned A or AAAA record with your current public address.
- Restart the app once to confirm the configuration is persistent.
DDNS only keeps a hostname pointed to an address; it does not by itself create a secure remote-access path. If the end goal is remote access to a home server, compare this with the connection model described in Zima Client remote access before exposing services directly.
Provider Changes and IPv6
If you use Cloudflare or another provider, remove the DuckDNS-specific fields and follow that provider's schema. For example, the current Cloudflare configuration uses fields such as zone identifier and an API token; the upstream Cloudflare provider documentation is the source of truth.
FAQ
Why is my appdata/ddns-updater folder missing?
The persistent host path may differ from the path used in the community example. Check the app's volume mapping rather than creating a guessed system path.
Can I use IPv4 and IPv6?
Yes, but configure the IP-version option according to the current provider documentation and confirm your ISP actually provides the address family you intend to publish.
Is DDNS the same as a VPN?
No. DDNS maps a hostname to a changing IP address. Authentication, encryption, firewall rules and remote-access design are separate concerns.
