ally9696
commented
3 years ago Alternatively try to set the DNS records with own API using your DNS provider template and look if the issue persists.
Open resaperk opened 3 years ago
ally9696
commented
3 years ago Alternatively try to set the DNS records with own API using your DNS provider template and look if the issue persists.
resaperk
commented
3 years ago Using api, and the constellix admin panel, multiple text records with the same name will error
They expect (in this case) both challenge TXT records to be added at once for the domain, i.e.
[
{
"type":"txt",
"add":true,
"set":{
"name":"_acme-challenge",
"ttl":120,
"roundRobin":[
{"value":"CHALLENGE1ABCD1234ABCD1234ABCD1234ABCD1234A"},
{"value":"CHALLENGE2ABCD1234ABCD1234ABCD1234ABCD1234A"}
]
}
}
]
mrlindstrom
commented
3 years ago Adding a response from the Constellix team regarding this:
So just to clarify, the way records are organized in our system is instead of having multiple TXT records with the same hostname, it is organized as one TXT record with multiple values (the body of the call I pasted in my last reply is 4 values in 1 record). If you already have an existing TXT record of the same hostname then you would need to do a PUT instead of POST. The best way to manage this is to first GET the TXT record, then add additional values into the body of the call and send it back to our API as a PUT. Please let us know if you have further questions, we're happy to help!
So it looks like possibly changing to a PUT might address the issue for multiple records.
woutd
commented
3 years ago I have added support for updating existing TXT records that is required for certain wildcard certificates.
https://github.com/woutd/acme.sh/blob/constellix-wildcard-support/dnsapi/dns_constellix.sh
I will create a PR.
When trying to issue a cert for example.com and *.example.com, using dns-01 with constellix, dns_constellix.sh attempts to create the same TXT record for "_acme-challenge.example.com" twice, and fails "already exists" on the second
Steps to reproduce
Debug log