Just one _acme-challenge value for all domains in same DNS validation

Not in the sense that's being discussed here. If your DNS host has an API that certbot can use to automatically update entries, that's great--you really should be using it, and in that case your issue becomes moot.

But if not, what Osiris is recommending is acme-dns:

Which is designed for exactly this purpose.

2 Likes

Also, the ACME client acme.sh has a DNS plugin for GratisDNS.dk:

And also a "third party" DNS plugin for acme.sh for GratisDNS.dk exists:

It shouldn't be too hard to modify those scripts slightly to work as --manual-auth-hook and --manual-cleanup-hook scripts for the manual plugin. See User Guide — Certbot 1.16.0.dev0 documentation for more about those options.

1 Like

I want to stress that all the reasons your want this feature implemented are either due to:

  • an incredibly bad DNS server, or
  • incorrect usage of your DNS server

Your posts have increasingly made it clear that you are not using your DNS server correctly. You are implementing anti-patterns.

Populating the TXT records of every domain in the AcmeOrder with each and every domain's acme_challenge is an anti-pattern. This is creating unnecessary work for you, the DNS server, and LetsEncrypt's Boulder server that verifies challenges.

And a reminder that, aside from any security concerns, what you propose would ultimately create more problems for all users than solutions - as I mentioned above.

The limit of 10 appears to be the max number of TXT records that your DNS server allows, which is very reasonable. you are using an anti-pattern to manage DNS. You should not be updating all domains with the same TXT records. You should only be updating the actual affected domains with their specific TXT records.

5 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.