mholt/caddy-dynamicdns sits at 372 stars on GitHub, written primarily in Go. Caddy app that keeps your DNS records (A/AAAA) pointed at itself.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
This is a simple Caddy app that keeps your DNS pointed to your machine; especially useful if your IP address is not static.
It simply queries a service (an "IP source") for your public IP address every so often and if it changes, it updates the DNS records with your configured provider. It supports multiple IPs, including IPv4 and IPv6, as well as redundant IP sources.
IP sources and DNS providers are modular. This app comes with IP source modules. However, you'll need to plug in a DNS provider module from caddy-dns so that your DNS records can be updated.
[!NOTE]
This is not an official repository of the Caddy Web Server organization.
This updates DNS records for example.com via Cloudflare's API. (Notice how the DNS zone is separate from record names/subdomains.)
Complex example config
Here's a more filled-out config, will all the options used.
This config prefers to get the IP address locally via UPnP (if edge router has UPnP enabled, of course), but if that fails, will fall back to querying icanhazip.com for the IP address. If those fail, it will try to find the IP address from the eth0 interface. It then updates records for example.com, www.example.com, and subdomain.example.net. Notice how the zones and subdomains are separate; this eliminates ambiguity since we don't have to try to be clever and figure out the zone via recursive, authoritative DNS lookups. We also check every 5 minutes instead of 30 minutes (default), and set a TTL of 1 hour for the records.
The interface option will return at most 1 IPv4 and 1 IPv6 address. It will only return addresses that are not private according to RFC 1918 (IPv4) and RFC 4193 (IPv6), and is a global unicast address according to RFC 1122, RFC 4632, and RFC 4291 with the exception of IPv4 directed broadcast addresses.
Note that it's redundant to specify both IP versions in the config, since the default is to enable both IPv4 and IPv6. It's purpose is to allow disabling one or the other if your server is only reachable via one of the versions. It's included in this config example for posterity.
(Notice how the syntax is: <zone> [ @ | <subdomains...> ] -- zone first, then any subdomains; if no subdomains, then "@" is implied; if you do list subdomains and you want the zone root to be included, you have to add "@" explicitly.)
The provider directive can be repeated to update domains across multiple DNS providers, or across multiple accounts of the same provider (e.g. different API credentials per domain). Each provider's domains are configured with a domains block inside that provider's block:
Inside a provider's block, the name domains is reserved for this app; everything else belongs to the DNS provider module as usual (whether inline arguments or block subdirectives). All other options (ip_source, check_interval, versions, include/exclude, ttl, update_only, dynamic_domains) remain global and apply to all providers.
Note that repeating the whole dynamic_dns global option does not work — Caddy keeps only the last occurrence. Use multiple provider blocks within a single dynamic_dns option instead.
Disabling IPv4
To disable IPv4 lookups and use your unique global unicast IPv6 address, specify only IPv6 as the version you want enabled and use your machine interface to get the IP address:
There is an option dynamic_domains that can scan through the configured domains configured in this Caddy instance and will try to manage the DNS of those domains.
Note:
Only host matchers at the top-level of server routes will get managed.
on_demand is not supported because the hostname isn't known at config time.
Caddyfile config:
{
dynamic_dns {
provider cloudflare {env.CLOUDFLARE_API_TOKEN}
domains {
example.com @ www
example.net subdomain
}
dynamic_domains
}
}
# This domain will be managed.
cool.example.com {
redir http://google.com
}
# This domain will *NOT* be managed because it's not configured in dynamic_dns.
another.host.com {
redir http://youtube.com
}
Equivalent JSON config:
{
"apps": {
"dynamic_dns": {
"domains": {
"example.com": ["@", "www"],
"example.net": ["subdomain"]
},
"dynamic_domains": true,
"dns_provider": {
"name": "cloudflare",
"api_token": "topsecret"
},
},
"servers": {
"srv0": {
"routes": [{
// omitted
"match": [{
"host": [
// This domain will be managed.
"cool.example.com"
]
}]
}, {
// omitted
"match": [{
"host": [
// This domain will *NOT* be managed because it's not configured in dynamic_dns.
"another.host.com"
]
}]
}]
}
}
}
}
Does mholt/caddy-dynamicdns have a project website?
No homepage URL was recorded for mholt/caddy-dynamicdns in TopGit's last sync. The README tab above frequently contains screenshots and demo links, or check the repository description on GitHub.
Does mholt/caddy-dynamicdns have any tags?
TopGit's last sync did not record any GitHub topics for mholt/caddy-dynamicdns. GitHub topics appear in the right sidebar of a repository page; that's the authoritative place to check.
How active is development on mholt/caddy-dynamicdns?
The most recent commit recorded on mholt/caddy-dynamicdns was 2 months ago, based on the GitHub push timestamp. The repository has 41 forks — one of the better signals of community interest.
How many stars does mholt/caddy-dynamicdns have?
mholt/caddy-dynamicdns has 372 GitHub stars — refresh the page for the live number, or check github.com/mholt/caddy-dynamicdns. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is mholt/caddy-dynamicdns open source?
Yes — mholt/caddy-dynamicdns ships under the Apache-2.0 license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/mholt/caddy-dynamicdns.
Where do I read more about mholt/caddy-dynamicdns?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/mholt/caddy-dynamicdns is the definitive source.
Read full README in the tab above.
Is caddy-dynamicdns worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of caddy-dynamicdns.
/caddy-dynamicdns