mirror of
https://github.com/acme-dns/acme-dns.git
synced 2026-04-27 12:55:48 +03:00
[GH-ISSUE #391] Confusing output of the script during validation #222
Labels
No labels
Documentation
Documentation
bug
enhancement
feature request
feature request
help wanted
pull-request
question
security
security
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/acme-dns#222
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Linuxmaker on GitHub (Aug 12, 2025).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/391
The "acme-dns" script is installed on a Debian Bookworm along with Certbot 2.1.0 via APT. This command
~# certbot certonly --manual --manual-auth-hook /etc/letsencrypt/acme-dns-auth.py --preferred-challenges dns --debug-challenges -d \*.example.com -d example.comreturns this confusing message:
If this line is entered exactly as it is in the corresponding zone file, DNS BIND will fail. The DNS server will think _acme-challenge.example.com.example.com is the correct resolution. But that's wrong.
My suggestion would be that the output when requesting to add the entry to the zone file should either include a trailing period
_acme-challenge.example.com. CNAME 47eddf55-38fa-4d22-b85a-872b2375c9bb.auth.acme-dns.io.or output this entry without a period:
_acme-challenge CNAME 47eddf55-38fa-4d22-b85a-872b2375c9bb.auth.acme-dns.io.Anyone who doesn't know how DNS servers work will fail at this point. It may be that this entry works for Internet service providers. In that case, this difference should be published in the instruction.
Best regards
Andreas Günther