Updated dnsapi2 (markdown)

Sergey Ponomarev 2023-06-07 00:57:08 +03:00
parent 6c52326683
commit 70cedd0240
1 changed files with 15 additions and 11 deletions

@ -88,7 +88,7 @@
## 76. Use Schlundtech
[Schlundtech](https://www.schlundtech.de/) offers a [xml api](https://www.schlundtech.de/services/xml-gateway/) with your standard login credentials, set them like so:
[Schlundtech](https://www.schlundtech.de/) offers a [xml api](https://www.schlundtech.de/services/xml-gateway/) with your standard login credentials, set them like so:
```sh
export SCHLUNDTECH_USER="yourusername"
@ -146,7 +146,8 @@ Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2103)
## 78. Use AcmeProxy DNS API
[Acmeproxy](https://github.com/mdbraber/acmeproxy/) can be used to as a single host in your network to request certificates through a DNS API. Clients can connect with one single host (the acmeproxy) so you don't need to store your DNS API credentials on every single host that wants to request a certificate.
[Acmeproxy](https://github.com/mdbraber/acmeproxy/) can be used to as a single host in your network to request certificates through a DNS API.
Clients can connect with one single host (the acmeproxy) so you don't need to store your DNS API credentials on every single host that wants to request a certificate.
```sh
export ACMEPROXY_ENDPOINT="https://acmeproxy.yourhost.com:9096"
@ -333,7 +334,7 @@ UpdateDNSZone():ALLOW
Remember the role id and role password.
```sh
export Hexonet_Login="stokito!turris"
export Hexonet_Login="user!role"
export Hexonet_Password="<role password>"
```
@ -406,7 +407,8 @@ Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2480)
## 87. Use the RcodeZero API to automatically issue cert
First you need to login to your RcodeZero account, enable the REST API and generate an ACME API token (only the ACME API token will work wih acme.sh. It has limited access and could only be used to add/remove challenges to the zones).
First you need to login to your RcodeZero account, enable the REST API and generate an ACME API token.
Only the ACME API token will work wih acme.sh. It has limited access and could only be used to add/remove challenges to the zones.
https://my.rcodezero.at/enableapi
@ -570,7 +572,8 @@ https://github.com/Neilpang/acme.sh/issues/2577
[PDNS Manager](https://pdnsmanager.org/) is a web frontend for [Power DNS](https://www.powerdns.com/).
This script uses PDNS Manager API and its "[Update via GET request](https://pdnsmanager.org/documentation/api/)" method. So only single record update possible and no wildcards, for now.
This script uses PDNS Manager API and its [Update via GET request](https://pdnsmanager.org/documentation/api/) method.
So only single record update possible and no wildcards, for now.
```sh
export PDNS_MANAGER_URL="https://mypdnsmanagerurl.nx"
@ -650,15 +653,15 @@ Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2699)
<a name="dns_dynv6"/>
## 97. Use dynv6 API to automatically issue a cert
This uses the [dynv6 SSH API](https://dynv6.com/docs/apis) to issue the certificate.
This uses the [HTTP REST API](https://dynv6.github.io/api-spec/).
For this you will need a HTTP Token, which you can generate from the [dynv6 website](https://dynv6.com/keys).
Use it with `export DYNV6_TOKEN="value"`.
Alternatively you can use the [dynv6 SSH API](https://dynv6.com/docs/apis) to issue the certificate.
You will need a ssh key to authenticate.
You can specify your own key with `export KEY="path/to/keyfile"` or if no key is specified one will be created for you which you will have to add [here](https://dynv6.com/keys).
In both cases the path to the keyfile will be saved for reuse.
Alternatively you can use the [HTTP REST API](https://dynv6.github.io/api-spec/).
For this you will need a HTTP Token, which you can generate from the [dynv6 website](https://dynv6.com/keys).
Use it with `export DYNV6_TOKEN="value"`.
If both a SSH Key and a HTTP Token are specified the REST API will be used.
To issue a cert use:
@ -1090,7 +1093,8 @@ Report any issues [here](https://github.com/acmesh-official/acme.sh/issues/3088)
This provider supports the [Akamai Edge DNS](https://developer.akamai.com/api/cloud_security/edge_dns_zone_management/v2.html) API for creating DNS records.
This provider requires Akamai Open Edgegrid Credentials with EdgeDNS API access authorization. To create and establish your Akamai OPEN CREDENTIALS, see the [authorization](https://developer.akamai.com/legacy/introduction/Prov_Creds.html) and [credentials](https://developer.akamai.com/legacy/introduction/Conf_Client.html) sections of the Akamai Developer Get Started guide.
This provider requires Akamai Open Edgegrid Credentials with EdgeDNS API access authorization.
To create and establish your Akamai OPEN CREDENTIALS, see the [authorization](https://developer.akamai.com/legacy/introduction/Prov_Creds.html) and [credentials](https://developer.akamai.com/legacy/introduction/Conf_Client.html) sections of the Akamai Developer Get Started guide.
The Akamai Open Edgegrid credentials must be specified as environment variables as follows:
```sh