[GH-ISSUE #12] Does this work with latest certbot #9

Open
opened 2026-03-13 16:24:27 +03:00 by kerem · 1 comment
Owner

Originally created by @patrickshan on GitHub (Oct 5, 2021).
Original GitHub issue: https://github.com/acme-dns/acme-dns-client/issues/12

Hi there,

After setting up acme-dns and acme-dns-client, I still got this error when using it to renew certificate:

sudo certbot certonly --manual --preferred-challenges dns --manual-auth-hook 'acme-dns-client' -d my-domain.com -d \*.my-domain.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Renewing an existing certificate for my-domain.com and *.my-domain.com

Certbot failed to authenticate some domains (authenticator: manual). The Certificate Authority reported these problems:
  Domain: my-domain.com
  Type:   dns
  Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.my-domain.com - check that a DNS record exists for this domain

  Domain: my-domain.com
  Type:   dns
  Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.my-domain.com - check that a DNS record exists for this domain

After reading some upstream issues from certbot, it seems that this issue is still open: https://github.com/certbot/certbot/issues/6566. Does this mean current release of certbot client doesn't support CNAME ? If that's the case, any workaround ? I was trying to build a certbot client with that branch but apparently that branch was a bit too old to merge into latest master.

Thanks

Originally created by @patrickshan on GitHub (Oct 5, 2021). Original GitHub issue: https://github.com/acme-dns/acme-dns-client/issues/12 Hi there, After setting up acme-dns and acme-dns-client, I still got this error when using it to renew certificate: ``` sudo certbot certonly --manual --preferred-challenges dns --manual-auth-hook 'acme-dns-client' -d my-domain.com -d \*.my-domain.com Saving debug log to /var/log/letsencrypt/letsencrypt.log Renewing an existing certificate for my-domain.com and *.my-domain.com Certbot failed to authenticate some domains (authenticator: manual). The Certificate Authority reported these problems: Domain: my-domain.com Type: dns Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.my-domain.com - check that a DNS record exists for this domain Domain: my-domain.com Type: dns Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.my-domain.com - check that a DNS record exists for this domain ``` After reading some upstream issues from certbot, it seems that this issue is still open: https://github.com/certbot/certbot/issues/6566. Does this mean current release of certbot client doesn't support CNAME ? If that's the case, any workaround ? I was trying to build a certbot client with that branch but apparently that branch was a bit too old to merge into latest master. Thanks
Author
Owner

@maddes-b commented on GitHub (Jan 1, 2025):

I use acme-dns-client-2 with certbot and acme-dns.
Other acme-dns clients for certbot should work too.

Please check your DNS setup and re-try. Close issue when done.

<!-- gh-comment-id:2567071804 --> @maddes-b commented on GitHub (Jan 1, 2025): I use [acme-dns-client-2](https://github.com/maddes-b/acme-dns-client-2) with certbot and acme-dns. Other acme-dns clients for certbot should work too. Please check your DNS setup and re-try. Close issue when done.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/acme-dns-client#9
No description provided.