Add DNS API support for Nexcess, Thermo.io, and Futurehosting

[laszlof]

This adds DNS support for Nexcess, Futurehosting, and Thermo.io

All 3 use the same API backend (different endpoints), so the code is mostly identical other than the names of things.

[Neilpang]

please check this guide https://github.com/Neilpang/acme.sh/wiki/DNS-API-Dev-Guide

[laszlof]

@Neilpang Thanks. I have read through the guide. Is there something specific I am missing from it?

[laszlof]

@Neilpang is there anything additional that is needed on this PR?

[laszlof]

Bumping this back up. Anything needed on my end @Neilpang?

[laszlof]

Merge Conflicts Resolved.

[laszlof]

Conflicts Resolved. (Again).

[Neilpang]

https://github.com/Neilpang/acme.sh/wiki/DNS-API-Dev-Guide

please make sure you can handle all the domains:

_acme-challenge.www.example.com
_acme-challenge.example.com
_acme-challenge.example.co.uk
_acme-challenge.www.example.co.uk
_acme-challenge.sub1.sub2.www.example.co.uk

And support v2 wildcard:
#1261

[laszlof]

All issues have been corrected.

Also confirmed that it works with all example, including v2 wildcard.

[Neilpang]

Sorry, I just noticed that you said these 3 apis are identical.
I wonder if we can use only script to handle all the 3 ?

export   XXX_AccessToken=xxxxxxx
export  XXX_Endpoint="https://my.futurehosting.com/"

acme.sh --issue  -d example.com  --dns  dns_xxx.sh 

We can save XXX_AccessToken and XXX_Endpoint

what do you think ?

[laszlof]

@Neilpang Thats actually a good idea. I'll work out the details and update the PR

[laszlof]

Do not merge yet. Still need to do some final testing.

[laszlof]

@Neilpang This has been tested and should be good to go.

[Neilpang]

please close this PR, and make a new one.

Thanks.

[laszlof]

Done. #2082