[GH-ISSUE #323] Support of DuckDNS.org API #176

New issue

Closed

opened 2026-03-13 16:02:50 +03:00 by kerem · 1 comment

kerem commented

2026-03-13 16:02:50 +03:00

Owner

Originally created by @stokito on GitHub (Dec 22, 2022).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/323

Hi @joohoi thank you for your project. I came with a similar idea.
But I need more simple API that will use only GET request. Yes, it's not nice but there is a reason for this.
Please read the thread
https://community.letsencrypt.org/t/dns-api-standard-or-specification/189887/6

Originally created by @stokito on GitHub (Dec 22, 2022). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/323 Hi @joohoi thank you for your project. I came with a similar idea. But I need more simple API that will use only GET request. Yes, it's not nice but there is a reason for this. Please read the thread https://community.letsencrypt.org/t/dns-api-standard-or-specification/189887/6

kerem closed this issue

2026-03-13 16:02:56 +03:00

kerem commented

2026-03-13 16:03:01 +03:00

Author

Owner

@joohoi commented on GitHub (Jan 3, 2023):

Hi, thanks for opening the issue.

I'm having a bit hard time understanding the scenario here. Using acme-dns for DNS validation should not require the user to do anything else on their DNS zone than to create a single permanent CNAME record and the acme-dns server itself doesn't do any API integrations itself.

@joohoi commented on GitHub (Jan 3, 2023): Hi, thanks for opening the issue. I'm having a bit hard time understanding the scenario here. Using acme-dns for DNS validation should not require the user to do anything else on their DNS zone than to create a single permanent CNAME record and the acme-dns server itself doesn't do any API integrations itself.