History

Philippe Kueck 54d61bdc4a - get rid of bash-only syntax like ${foo:-bar} - use sh instead of bash - remove redundant functions _info, _err, _debug and _debug2 - get rid of mktemp, pipe commands directly to nsupdate		2016-10-26 16:14:47 +02:00
..
dns_cf.sh	add dns_xxx_rm function	2016-10-25 23:08:02 +08:00
dns_cx.sh	add dns_xxx_rm function	2016-10-25 23:08:02 +08:00
dns_dp.sh	add dns_xxx_rm function	2016-10-25 23:08:02 +08:00
dns_gd.sh	add dns_xxx_rm function	2016-10-25 23:08:02 +08:00
dns_lexicon.sh	add dns_xxx_rm function	2016-10-25 23:08:02 +08:00
dns_myapi.sh	add dns_xxx_rm function	2016-10-25 23:08:02 +08:00
dns_nsupdate.sh	- get rid of bash-only syntax like ${foo:-bar}	2016-10-26 16:14:47 +02:00
dns_ovh.sh	add dns_xxx_rm function	2016-10-25 23:08:02 +08:00
dns_pdns.sh	add dns_xxx_rm function	2016-10-25 23:08:02 +08:00
README.md	use RFC2606 example.com domain in docs (#327 )	2016-10-13 10:14:36 +08:00

How to use dns api

Use CloudFlare domain api to automatically issue cert

For now, we support clourflare integeration.

First you need to login to your clourflare account to get your api key.

export CF_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"

export CF_Email="xxxx@sss.com"

Ok, let's issue cert now:

acme.sh   --issue   --dns dns_cf   -d example.com  -d www.example.com

The CF_Key and CF_Email will be saved in ~/.acme.sh/account.conf, when next time you use cloudflare api, it will reuse this key.

For now, we support dnspod.cn integeration.

First you need to login to your dnspod.cn account to get your api key and key id.

export DP_Id="1234"

export DP_Key="sADDsdasdgdsf"

Ok, let's issue cert now:

acme.sh   --issue   --dns dns_dp   -d example.com  -d www.example.com

The DP_Id and DP_Key will be saved in ~/.acme.sh/account.conf, when next time you use dnspod.cn api, it will reuse this key.

For now, we support Cloudxns.com integeration.

First you need to login to your Cloudxns.com account to get your api key and key secret.

export CX_Key="1234"

export CX_Secret="sADDsdasdgdsf"

Ok, let's issue cert now:

acme.sh   --issue   --dns dns_cx   -d example.com  -d www.example.com

The CX_Key and CX_Secret will be saved in ~/.acme.sh/account.conf, when next time you use Cloudxns.com api, it will reuse this key.

We support Godaddy integration.

First you need to login to your Godaddy account to get your api key and api secret.

Please Create a Production key, instead of a Test key.

export GD_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"

export GD_Secret="asdfsdafdsfdsfdsfdsfdsafd"

Ok, let's issue cert now:

acme.sh   --issue   --dns dns_gd   -d example.com  -d www.example.com

The GD_Key and GD_Secret will be saved in ~/.acme.sh/account.conf, when next time you use cloudflare api, it will reuse this key.

We support PowerDNS embedded API integration.

First you need to enable api and set your api-token in PowerDNS configuration.

export PDNS_Url="http://ns.example.com:8081"
export PDNS_ServerId="localhost"
export PDNS_Token="0123456789ABCDEF"
export PDNS_Ttl=60

Ok, let's issue cert now:

acme.sh   --issue   --dns dns_pdns   -d example.com  -d www.example.com

The PDNS_Url, PDNS_ServerId, PDNS_Token and PDNS_Ttl will be saved in ~/.acme.sh/account.conf.

If your api is not supported yet, you can write your own dns api.

Let's assume you want to name it 'myapi',

Create a bash script named ~/.acme.sh/dns_myapi.sh,
In the script, you must have a function named dns_myapi_add(). Which will be called by acme.sh to add dns records.
Then you can use your api to issue cert like:

acme.sh  --issue  --dns  dns_myapi  -d example.com  -d www.example.com

For more details, please check our sample script: dns_myapi.sh