Updated dnsapi (markdown)
parent
539a184659
commit
40941a366e
12
dnsapi.md
12
dnsapi.md
|
@ -1198,7 +1198,7 @@ The TELE3_Key and TELE3_Secret will be saved in `~/.acme.sh/account.conf` and wi
|
||||||
|
|
||||||
<a name="dns_euserv" />
|
<a name="dns_euserv" />
|
||||||
|
|
||||||
## 47. Use Euserv.eu API
|
## 47. Use EUserv.eu API
|
||||||
|
|
||||||
First you need to login to your euserv.eu account and activate your API Administration (API Verwaltung).
|
First you need to login to your euserv.eu account and activate your API Administration (API Verwaltung).
|
||||||
[https://support.euserv.com](https://support.euserv.com)
|
[https://support.euserv.com](https://support.euserv.com)
|
||||||
|
@ -1208,17 +1208,17 @@ Please specify the scope (active groups: domain) and assign the allowed IPs.
|
||||||
|
|
||||||
```sh
|
```sh
|
||||||
export EUSERV_Username="99999.user123"
|
export EUSERV_Username="99999.user123"
|
||||||
export EUSERV_Password="Asbe54gHde"
|
export EUSERV_Password="<password>"
|
||||||
```
|
```
|
||||||
|
|
||||||
Ok, let's issue a cert now: (Be aware to use the `--insecure` flag, cause euserv.eu is still using self-signed certificates!)
|
Ok, let's issue a cert now: (Be aware to use the `--insecure` flag, because the euserv.eu is still using self-signed certificates!)
|
||||||
```sh
|
```sh
|
||||||
./acme.sh --issue --dns dns_euserv -d example.com -d *.example.com --insecure
|
./acme.sh --issue --dns dns_euserv -d example.com -d *.example.com --insecure
|
||||||
```
|
```
|
||||||
|
|
||||||
The `EUSERV_Username` and `EUSERV_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
The `EUSERV_Username` and `EUSERV_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||||
|
|
||||||
Report any bugs or issues [here](https://github.com/initit/acme.sh) or to <github@initit.de>
|
Report any bugs or issues to <github@initit.de>
|
||||||
|
|
||||||
|
|
||||||
<a name="dns_dpi" />
|
<a name="dns_dpi" />
|
||||||
|
@ -1258,7 +1258,7 @@ You can change the configuration being used without *activating* it; simply set
|
||||||
To issue a certificate you can:
|
To issue a certificate you can:
|
||||||
```sh
|
```sh
|
||||||
export CLOUDSDK_ACTIVE_CONFIG_NAME=default # see the note above
|
export CLOUDSDK_ACTIVE_CONFIG_NAME=default # see the note above
|
||||||
./acme.sh --issue --dns dns_gcloud -d example.com -d '*.example.com'
|
./acme.sh --issue --dns dns_gcloud -d example.com -d *.example.com
|
||||||
```
|
```
|
||||||
|
|
||||||
`dns_gcloud` also supports [DNS alias mode](https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mode).
|
`dns_gcloud` also supports [DNS alias mode](https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mode).
|
||||||
|
@ -1772,7 +1772,7 @@ Ensure that the acme.sh process has write access to the zone file and read acces
|
||||||
|
|
||||||
Issuing a certificate:
|
Issuing a certificate:
|
||||||
```sh
|
```sh
|
||||||
./acme.sh --issue --dns dns_maradns -d example.com -d '*.example.com'
|
./acme.sh --issue --dns dns_maradns -d example.com -d *.example.com
|
||||||
```
|
```
|
||||||
|
|
||||||
`MARA_ZONE_FILE` and `MARA_DUENDE_PID_PATH` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
`MARA_ZONE_FILE` and `MARA_DUENDE_PID_PATH` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||||
|
|
Loading…
Reference in New Issue