Namecheap DDNS Updater
Namecheap DDNS Updater is a lightweight container that automatically updates your Namecheap Dynamic DNS (DDNS) records for multiple hosts at a set interval.
Platform availability
Available on 1 of 10 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)
- Any server (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.
19/100 Low
- Maintained
- 17last commit 564 days ago
- Popular
- 102 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 26 days ago
- GitHub stars
- 2
- Open issues
- 0
- Last commit
- 2025-05-06
- Activity
- stale
Checked 8 days ago - source: GitHub (tranceer/nraid-namecheap-ddns-updater)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Add Namecheap login details In the provider block, enter your Namecheap username, API key, and client_ip (the IP the updater connects from), then set use_sandbox = false. If these are missing or wrong, Namecheap rejects the API call and DNS won't update. source
- Choose MERGE to avoid deleting DNS If you only want the updater to manage one or two hosts, use mode = "MERGE" so other DNS records stay untouched. Using OVERWRITE can remove records you didn't list, which may break your website or email. source
- Set mail settings when overwriting If your domain receives or forwards email, choose an email_type such as FWD or MX and add the matching MX records. Skipping this while overwriting DNS can leave email misrouted and make incoming mail fail. source
- Setup prerequisites Before running, create an A record for @.yourdomain.com, add a CNAME record for each subdomain you want to track, enable Dynamic DNS in your Namecheap dashboard, and copy the API key into the container. source
Fetched 45 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I make the container update multiple Namecheap hosts?
Set HOSTS to a comma-separated list of hosts to update. The README shows an example such as @,www,admin.
Can I change the updater logic after the container starts?
Yes, the container includes an entrypoint.sh script that can be edited inside the container for advanced customization.
What should I check if DNS records are not resolving after an update?
Check that you are not using Namecheap's nameserver as the query destination. Use the nameservers responsible for answering queries for the domain.
What workaround has been reported for Let's Encrypt DNS challenge issues with Namecheap Dynamic DNS?
One reported fix is to add the domain to Cloudflare and set Namecheap's DNS servers to Cloudflare. Then use the Cloudflare API key to complete the DNS challenge.
Answers sourced from github.com, www.reddit.com, www.reddit.com
Community
- r/selfhosted on Reddit: Recommendations for Dynamic DNS updaters (free ... (reddit)
- A warning about Namecheap when using dynamic DNS, Let's ... - Reddit (reddit)
- Namecheap DDNS not supported on most routers, any way around ... - Reddit (reddit)
- DDNS update not working on 388.1 - SmallNetBuilder Forums (forum)
- DDNS via Namecheap | SNBForums - SmallNetBuilder Forums (forum)
Collected 53 days ago - public community threads