[GH-ISSUE #331] acme-dns only saves a single TXT record, not 2 #183

New issue

Open

opened 2026-03-13 16:04:29 +03:00 by kerem · 0 comments

kerem commented

2026-03-13 16:04:29 +03:00

Owner

Originally created by @Exagone313 on GitHub (Feb 12, 2023).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/331

Hello,

I have acme-dns v1.0 self-hosted and I'm trying to use it along with dehydrated to create a wildcard certificate (with both foo.example and *.foo.example in alt names in the same certificate).

This requires being able to return two different TXT records for solving both challenges at the same time.

However, each time I call the /update endpoint, the TXT record is updated and acme-dns will only send a single TXT record for my domain. This means that when the challenges are checked, the first challenge will be invalid (since only the second one is returned).

Unfortunately, dehydrated doesn't support handling one challenge at once (see the issue here), unlike cert-manager on Kubernetes (by specifying --max-concurrent-challenges=1). dehydrated requires all challenges to be valid at once, before it asks the server to check the challenges.

This seems like a regression from #28.

Do you have the same issue?

Originally created by @Exagone313 on GitHub (Feb 12, 2023). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/331 Hello, I have acme-dns v1.0 self-hosted and I'm trying to use it along with [dehydrated](https://github.com/dehydrated-io/dehydrated) to create a wildcard certificate (with both `foo.example` and `*.foo.example` in alt names in the same certificate). This requires being able to return two different TXT records for solving both challenges at the same time. However, each time I call the `/update` endpoint, the TXT record is updated and acme-dns will only send a single TXT record for my domain. This means that when the challenges are checked, the first challenge will be invalid (since only the second one is returned). Unfortunately, dehydrated doesn't support handling one challenge at once ([see the issue here](https://github.com/dehydrated-io/dehydrated/issues/554)), unlike cert-manager on Kubernetes (by specifying `--max-concurrent-challenges=1`). dehydrated requires all challenges to be valid at once, before it asks the server to check the challenges. This seems like a regression from #28. Do you have the same issue?