- Support for domains longer than 3 segments (ex. 1.www.mydomain.com).
- No need for GODADDY_BASE. Domain will be automatically determined from full RR name.
- Update to delete challenge records.
PUT now requires a relative domain name.
GET changed the order of name and data in the JSON.
Note: Due to the API changes, you may need to add
GODADDY_BASE to getssl.cfg. This is a space-separated
list of base domain names (zones) in which the challenge
responses are entered. There doesn't seem to be a way
around this that works in all cases, as the GoDaddy API
requires that the zone name be known.
rdbath suggested how to implement a timeout on s_client probes.
Unfortunately, wait -n is a bash 4.3 feature. So this requires
bash 4.3. CHECK_CERT_TIMEOUT can be used to override the default, which
is 4 seconds. Fallback is provided for older versions.
Views may require the 'nslookup' process to do somthing special, usually
provide a TSIG key or bind to a specific local address. Add a
hook for that - export the VARIABLE DNS_CHECK_FUNC_OPTIONS with the
desired options._Set DNS_CHECK_FUNC to the desired command, which
must be one of the supported ones: 'dig', 'drill', 'host' or 'nslookup'.
However, this turned up the fact that the dig/drill code had the domain
and record type arguments in the wrong order on the command line.
(The domain comes first, see the man page.) Fixed.
In some cases defining the previously undocumented PUBLIC_DNS_SERVER
may work. This commit adds it to the template file, and exports it
for the benefit of DNS_UPDATE scripts. Also AUTH_DNS_SERVER.
Squashed awk complaints about curl.header in some cases with debugging on.
Support older curl (--trace-time is somewhat recent)
-t FILE (or GODADDY_TFILE=FILE) will append command arguments
and all wire traffic to a file.
This provides all the information needed for debugging future issues.