github
/
acme.sh
mirror of https://github.com/acmesh-official/acme.sh
1
0
Fork 0
Code Issues Releases Wiki Activity

add anchors 1

master
Sergey Ponomarev 2023-06-06 14:14:49 +03:00
parent e09b11b95d
commit 1e7e71e765
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
dnsapi.md

@ -1391,6 +1391,7 @@ If you find any bugs of deSEC.io API, please report here: https://github.com/Ne
## 72. Use OpenProvider API ## 72. Use OpenProvider API
<a name="dns_openprovider" />
First, you need to enable API access and retrieve your password hash on https://rcp.openprovider.eu/account/dashboard.php First, you need to enable API access and retrieve your password hash on https://rcp.openprovider.eu/account/dashboard.php
@ -1406,6 +1407,7 @@ export OPENPROVIDER_PASSWORDHASH='xxx'
If you find any bugs of OpenProvider dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2104 If you find any bugs of OpenProvider dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2104
## 73. Use MaraDNS API ## 73. Use MaraDNS API
<a name="dns_maradns" />
Make sure you've configured MaraDNS properly and setup a zone file for your domain. See [`csv2(5)`](https://manpages.debian.org/stretch/maradns/csv2.5.en.html). Make sure you've configured MaraDNS properly and setup a zone file for your domain. See [`csv2(5)`](https://manpages.debian.org/stretch/maradns/csv2.5.en.html).
@ -1429,24 +1431,26 @@ Issuing a certificate:
If you find any bugs of MaraDNS DNS API, please report here: https://github.com/Neilpang/acme.sh/issues/2072 If you find any bugs of MaraDNS DNS API, please report here: https://github.com/Neilpang/acme.sh/issues/2072
## 74. Use Hetzner API ## 74. Use Hetzner API
<a name="dns_hetzner" />
Get the API Token: Get the API Token:
Use [dnsConsole](https://dns.hetzner.com/) to create your hetzner api token. Use [dnsConsole](https://dns.hetzner.com/) to create your hetzner api token.
Issuing a certificate (using letsencrypt): Issuing a certificate (using letsencrypt):
```sh ```sh
export HETZNER_Token="xxxx" export HETZNER_Token="<token>"
./acme.sh --issue --dns dns_hetzner -d example.com -d www.example.com --server letsencrypt ./acme.sh --issue --dns dns_hetzner -d example.com -d www.example.com --server letsencrypt
``` ```
## 75. Use DDNSS.de API ## 75. Use DDNSS.de API
<a name="dns_ddnss" />
First create an account at https://ddnss.de. After that create a new host record. First create an account at https://ddnss.de. After that create a new host record.
In the defenition for the host make sure to set the checkbox for "Wildcard" and for "TXT". In the definition for the host make sure to set the checkbox for "Wildcard" and for "TXT".
Note your Api Key (aka "Update Key") displayed at ddnss.de and export in DDNSS_Token variable Note your Api Key (aka "Update Key") displayed at ddnss.de and export in DDNSS_Token variable
```sh ```sh
export DDNSS_Token="e4155767few8erwf59353633tz342ce85werddc99432" export DDNSS_Token="<token>"
``` ```
**Note: Every Cert needs it own Update Key, if you already use the Update Key please generate a new one and export to DDNSS_Token before issue a new Cert. ** **Note: Every Cert needs it own Update Key, if you already use the Update Key please generate a new one and export to DDNSS_Token before issue a new Cert. **
@ -1459,6 +1463,7 @@ After that you can issue a new certificate:
If you find any bugs of ddnss.de API, please report here: https://github.com/Neilpang/acme.sh/issues/2230 If you find any bugs of ddnss.de API, please report here: https://github.com/Neilpang/acme.sh/issues/2230
## 76. Use NLnetLabs NSD ## 76. Use NLnetLabs NSD
<a name="dns_nsd" />
You need to export two variables. Your zonefile which the script will automatically edit: You need to export two variables. Your zonefile which the script will automatically edit:
```sh ```sh