Support Rackspace Cloud DNS
This commit is based on the original pull request by tcocca
https://github.com/Neilpang/acme.sh/pull/1297
Addtional cleanup was provided by senseisimple in
https://github.com/Neilpang/acme.sh/pull/1999
This pull request has squashed the changes for review, fixed a minor
(but breaking) problem with the field ordering in the response, and
added documenation per the API guide.
Co-Author: Chris <chris@chrisnovoa.com>
Co-Author: Ian Wienand <ian@wienand.org>
Default of a zone might be high, which is annoying when testing
with the ACME staging API. I think setting the TTL to 0 makes sense
as acme.sh is the only one checking this, so having an always up
to date response seems desirable.
Checks if a subdomain already exists before creating one. The loopia API clears all records for a subdomain when adding it again.
Adding TXT-records instead of updating the existing record when using the add method. Wildcard certificates require multiple TXT-records for the same subdomain.
Now you can create wildcard certificates using:
`acme.sh --issue -d example.com -d '*.example.com' --dns dns_loopia`
Double quoting variables
Gandi supports setting multiple entries by setting multiple array items
for the rrset_values field in their API. Modify the dns_gandi_livedns.sh
script so that it checks for existing entries, appends new ones if
needed, and removes existing ones individually. This enabled wildcard
certificate support on Gandi.
Fixes the dns_gandi_livedns part of #1261.
Tested for creating a multidomain, multiple wild-card certificate on
Gandi and using a test script executing only the dns_gandi_livedns_add
and dns_gandi_livedns_rm functions.
The Cloud and Classic Manager work with different APIs, and so require
a separate module, which we introduce here.
The README has also been modified to state that the two are separate
and incompatible, and provides instructions on using either.
