Using DuckDNS with custom domain reddit / selfhosted ---------------------------------------------------------------------- Odd-Let9042 · 2023-12-11 17:33 Hi, I have a duckdns subdomain that I use with NGINX to access my local network with SSL. I'm trying to point also a custom domain to it. As per duckdns FAQ, I create a CNAME record pointing "[local.customdomain.co](https://local.customdomain.co)" to my DuckDNS subdomain and the record is showing with a CNAME lookup. If I try the DNS Challenge in NGINX I get: Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-48" --agree-tos --email "xxxx@xxx.com" --domains "local.customdomain.co" --authenticator dns- duckdns --dns-duckdns-credentials "/etc/letsencrypt/credentials/credentials-48" --dns-duckdns- propagation-seconds 240 Saving debug log to /tmp/letsencrypt- log/letsencrypt.log Encountered exception during recovery: certbot.errors.PluginError: The given domain "[local.customdomain.co](https://local.customdomain.co)" is neither a duckdns subdomain nor delegates \_acme- challenge.[local.customdomain.co](https://local.customdomain.co) to a duckdns subdomain. The given domain "[local.customdomain.co](https://local.customdomain.co)" is neither a duckdns subdomain nor delegates \_acme- challenge.[local.customdomain.co](https://local.customdomain.co)" o a duckdns subdomain. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt- log/letsencrypt.log or re-run Certbot with -v for more details. at ChildProcess.exithandler (node:child\_process:402:12) at ChildProcess.emit (node:events:513:28) at maybeClose (node:internal/child\_process:1100:16) at Socket. (node:internal/child\_process:458:11) at Socket.emit (node:events:513:28) at Pipe. (node:net:301:12) I added also a CNAME record for "\_acme- challenge.[local.customdomain.co](https://local.customdomain.co)" but still no luck. Can you help me? Thanks! ---------------------------------------------------------------------- thekrautboy · 2023-12-11 17:46 Not sure if that is possible at all with DuckDNS, i havent used it myself in a long time. Try [deSEC.io](https://desec.io/) instead, its also free, run by a non-profit, no ads, no premium accounts, based in germany. They offer subdomains in the form of `example.dedyn.io` but you can also set your domains nameservers to theirs and manage your own domain DNS through their controlpanel. ---------------------------------------------------------------------- Odd-Let9042 · 2023-12-11 18:25 Thanks, I’ll give it a try! The procedure is followed is included in DuckDNS FAQ so it should be possible anyway. ---------------------------------------------------------------------- nik_h_75 · 2023-12-11 20:00 It's possible and works. What doesn't work (for me) is to point tld to duckdns and then get a let's encrypt SSL cert (via nginx Proxy Manager). I have to go subdomain.tld.xx to get it to work.