ACME certificate renewal/creation fails with multiple DNS providers
When trying to issue/renew ACME certificates to multiple different DNS providers with the DNS verification method, the verification fails. In my use case, I am using Dreamhost and Route 53 DNS verification.
When executing the issue/renewal, the ACME script uses the last credentials method's credentials for both verification methods.
If I set up Dreamhost first, then Route 52, then the script sends the AWS API credentials to Dreamhost.
If I set up Route 52 first, then Dreamhost, then the script sends the Dreamhost API credentials to Route 53.
Updated by Jim Pingle 9 months ago
Right, and there is also no solution yet, but it's all the same problem with multiple (different) credentials.
Depending on the use case you could make one certificate per domain name instead of combining them into one single certificate. Some software (e.g. haproxy) is more than capable of deciding to use different certificates based on SNI/hostname.