Open xentie opened 6 years ago
updated with the new logfile
@Neilpang I seem to have the same issue. My AWS account has access to a ton of DNS zones.
I am trying to get certs for '*.apps.cluster-e954.e954.ocp4.opentlc.com' and 'cluster-e954-api.e954.ocp4.opentlc.com' it writes the TXT entries into the 'ocp4.opentlc.com' zone (as _acme-challenge.apps.cluster-e954.e954 .ocp4.opentlc.com.) rather than into the zone that Let's Encrypt then validates. Which is e954.ocp4.opentlc.com
.
Is there a way to specify the hosted zone ID? If so I think I can work around this.
Steps to reproduce
Route53 Info: mydomain.com and test.mydomain.com are separate Hosted Zones, issue is whenever I run the below-mention command, the script added TXT entries on mydomain.com hostedzone and not on test.mydomain.com hostedzone.
acme.sh --issue --dns dns_aws -d "test.mydomain.com" -d "*.test.mydomain.com" --test --log
note: actual domains replaced with: test.mydomain.com and *.test.mydomain.com actual AWS Access Key ID replaced with: AWS_ACCESS_KEY_ID
You can see at 02:52:44-45|02:55:03|02:55:13 timestamp, it is reading/writing to the wrong hostedzone and the domain is wrong, it should be: