Primary domain: domain1
Secondary domain: domain2
Domain2 hosts our TXT records for Let’s Encrypt purposes. We created a CNAME locally that aliases “_acme-challenge.server.domain1.edu” to “_acme-challenge.server.domain2.net”.
We use DNS Made Easy and provide the API key for domain2.
Certify the Web creates a TXT record with a name of “_acme-challenge.server.domain1.edu.domain2”
The validation fails with the following message:
“Validation of the required challenges did not complete successfully. DNS problem: NXDOMAIN looking up TXT for _acme-challenge.server1.edu”
Let’s Encrypt follows the CNAME we setup and is expecting to validate a TXT record with a name of “_acme-challenge.server.domain2.net” I verified this by modifying the TXT record during the 60 second wait period, and the certificate was issued properly.
Is our configuration supported by the current version of Certify the Web?
Thanks in advance for any assistance.
Ethan A. Cooper