lexicon
duckdns
Our great sponsors
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lexicon
duckdns
-
PSA: unless you are using wildcard certificates, all your subdomains get published in a list of issued Let's Encrypt certificates. You can see if your subdomains are published here: https://crt.sh/
(1) https://github.com/caddy-dns/duckdns
-
What are y’all using to set up a domain on your LAN so that your services are like `whatever.local/gitea` instead of `192.168.0.50:8080`. Pretty sure I need a reverse proxy but I’ve never set one up that wasn’t publicly available, so I’m not sure if a different set of rules apply.
My domain provider is not supported by Caddy, so I use duckdns.org for dynamic dns and dns challenge - it can be routed to my domain (see https://github.com/caddy-dns/duckdns). It might be possible to use duckdns.org directly instead of buying a domain, but the url will be xxx.duckdns.org or similar. (e.g. gitea-xyz.duckdns.org routed to 192.168.0.50)
-
Router ports open but reverse proxy not working (Docker, Caddy, DuckDNS)
Why are you using the email global directive for DuckDNS? Why not just use the DuckDNS addon (Github) module?
-
Let's Encrypt ACME DNS alias mode
Also known as "DNS challenge delegation".
I have this implemented (with help) for the libdns plugin for DuckDNS, which can be used with Caddy.
So basically, you can use a free https://www.duckdns.org/ domain to solve DNS challenges, for your domain which may be managed by any other DNS provider.
https://github.com/caddy-dns/duckdns#challenge-delegation
I do this with my domain I have registered with Google Domains, because they have no API at all right now.
-
Synching iOS Contact/Calander to Nextcloud 22.0 - Localhost - NO SSL?
- Using caddy reverse proxy + https://github.com/caddy-dns/duckdns
-
Caddy + Namecheap + DuckDNS configuration
But if you need wildcard certs, then using duckdns makes a whole lot of sense because namecheap's DNS API is some hot garbage (requires fetching the entire set of DNS records for the zone, making your change, then pushing back up the entire set, as XML). The alternative is to use DNS challenge delegation, which is quite easy to do with the duckdns plugin for Caddy https://github.com/caddy-dns/duckdns#challenge-delegation
What are some alternatives?
extdns - External DNS for docker-compose
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
acme-tiny - A tiny script to issue and renew TLS certs from Let's Encrypt
acme.sh - A pure Unix shell script implementing ACME client protocol
dehydrated-bigip-ansible - Ansible based hooks for dehydrated to enable ACME certificate automation for F5 BIG-IP systems
lexicon - Manipulate DNS records on various DNS providers in a standardized way.
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water
CoreDNS - CoreDNS is a DNS server that chains plugins
letsencrypt - Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.
portfolio-site - Personal portfolio site built using SvelteKit and Tailwind CSS.