ddns-ipv64
This Docker container is a DDNS updater for Free DynDNS - ipv64.net.
Platform availability
Available on 1 of 9 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
37/100 Low
- Maintained
- 41last commit 320 days ago
- Popular
- 3133 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 7 days ago
- GitHub stars
- 33
- Open issues
- 0
- Last commit
- 2025-11-27
- License
- MIT
- Activity
- stale
Checked 4 days ago - source: GitHub (alcapone1933/docker-ddns-ipv64)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 15 days ago - source: Docker Hub image tags and published docs
First-install notes
- Fill in domains and IP sources first Before starting the container, set DOMAINS to your Cloudflare domains and set IP4_PROVIDER/IP6_PROVIDER to where your IP is read from (for testing, static or a mounted file is fine). If these are missing, the app won't know which DNS records to update or where to get your current IP. source
- Set PROXIED for proxied domains If some domains should use Cloudflare’s proxy (the orange-cloud setting), set PROXIED to the exact domains or a short expression like is(example.org). Without this, proxied domains can be left with the wrong DNS/proxy configuration. source
- Test with local IP files safely For a dry run, mount ip4.txt and ip6.txt into the container and set the providers to file:/ip4.txt and file:/ip6.txt. This lets you fake IP changes and check the setup without touching your live DNS. source
Fetched 15 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What should I do on a DS-Lite connection where no real public IPv4 address is available?
Set IPV4_ENABLED=no to disable IPv4 updates.
Can I update several ipv64.net domains with one container?
Yes, list them comma-separated in DOMAIN_IPV64. For multiple domains, use the Account Key in DOMAIN_KEY.
How does DOMAIN_PRAEFIX behave when multiple domains are configured?
Only one prefix can be set with DOMAIN_PRAEFIX_YES=yes and DOMAIN_PRAEFIX. The same prefix is applied to every configured domain.
How is the update interval configured?
Use CRON_TIME and CRON_TIME_DIG in the container environment. The example run command uses */15 * * * * for CRON_TIME and */30 * * * * for CRON_TIME_DIG.
Answers sourced from github.com
Community
Collected 14 days ago - public community threads