added missing "Report any bugs or issues" links
Sergey Ponomarev
parent
dc15339c3e
commit
d66d1efa5a
208
dnsapi2.md
208
dnsapi2.md
|
|
@ -104,7 +104,7 @@ Then you can issue your certificates with:
|
|||
|
||||
The `SCHLUNDTECH_USER` and `SCHLUNDTECH_PASSWORD` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2246)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2246)
|
||||
|
||||
|
||||
<a name="dns_one"/>
|
||||
|
|
@ -125,12 +125,14 @@ Note:
|
|||
It's no longer possible to add TXT Records with the Name `_acme-challenge` to the base Domain.
|
||||
To override the fallback value, you must use a CNAME and proxy it.
|
||||
For example:
|
||||
|
||||
CNAME _acme-challenge.yourdomain.com => proxy_acme-challenge.yourdomain.com
|
||||
The TXT Records have to be created on proxy_acme-challenge.yourdomain.com
|
||||
|
||||
The TXT Records have to be created on `proxy_acme-challenge.yourdomain.com`.
|
||||
Since the default CNAME TTL is 3600 seconds, it is recommended to leave the CNAME record.
|
||||
But if you would like to use the build-in SSL (for your Web-Site etc.) from one.com, you have to delete the Record.
|
||||
|
||||
You can set "ONECOM_KeepCnameProxy" to keep the CNAME record.
|
||||
You can set `ONECOM_KeepCnameProxy` to keep the CNAME record.
|
||||
|
||||
```sh
|
||||
export ONECOM_KeepCnameProxy=1
|
||||
|
|
@ -140,7 +142,7 @@ By default the CNAME record will be removed.
|
|||
|
||||
The `ONECOM_User`,`ONECOM_Password` and `ONECOM_KeepCnameProxy` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2103)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2103)
|
||||
|
||||
|
||||
<a name="dns_acmeproxy"/>
|
||||
|
|
@ -164,7 +166,7 @@ Then you can issue your certificates with:
|
|||
|
||||
The `ACMEPROXY_ENDPOINT`, `ACMEPROXY_USERNAME` and `ACMEPROXY_PASSWORD` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2251)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2251)
|
||||
|
||||
|
||||
<a name="dns_internetbs"/>
|
||||
|
|
@ -186,7 +188,7 @@ To issue a certificate run:
|
|||
|
||||
The `INTERNETBS_API_KEY` and `INTERNETBS_API_PASSWORD` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2261)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2261)
|
||||
|
||||
|
||||
<a name="dns_durabledns"/>
|
||||
|
|
@ -208,7 +210,7 @@ To issue a certificate run:
|
|||
|
||||
The `DD_API_User` and `DD_API_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2281)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2281)
|
||||
|
||||
|
||||
<a name="dns_regru"/>
|
||||
|
|
@ -228,8 +230,7 @@ To issue a certificate run:
|
|||
|
||||
The `REGRU_API_Username` and `REGRU_API_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
If you find any bugs of reg.ru API, please report here:
|
||||
https://github.com/Neilpang/acme.sh/issues/2336
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2336)
|
||||
|
||||
RU:
|
||||
|
||||
|
|
@ -262,7 +263,7 @@ export REGRU_API_Password='водим пароль каторый настрои
|
|||
```
|
||||
Настройки для авторизации `REGRU_API_Username` и `REGRU_API_Password` будут сохранены в `~/.acme.sh/account.conf` и будут использоваться повторно при необходимости из конфига acme.
|
||||
|
||||
Если вы обнаружите какие-либо ошибки в API reg.ru, сообщите об этом [здесь](https://github.com/Neilpang/acme.sh/issues/2336)
|
||||
Если вы обнаружите какие-либо ошибки в API reg.ru, сообщите об этом [здесь](https://github.com/acmesh-official/acme.sh/issues/2336)
|
||||
|
||||
|
||||
<a name="dns_vultr"/>
|
||||
|
|
@ -286,7 +287,7 @@ To issue a cert:
|
|||
|
||||
The `VULTR_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
If you find any bugs, please report [here](https://github.com/Neilpang/acme.sh/issues/2374)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2374)
|
||||
|
||||
|
||||
<a name="dns_jd"/>
|
||||
|
|
@ -316,7 +317,7 @@ export JD_ACCESS_KEY_SECRET="<secret>"
|
|||
export JD_REGION="cn-north-1" # 这里写你要改的区域
|
||||
```
|
||||
|
||||
有 bug 的话可以报到这里: https://github.com/Neilpang/acme.sh/issues/2388
|
||||
有 bug 的话可以报到这里: https://github.com/acmesh-official/acme.sh/issues/2388
|
||||
|
||||
|
||||
<a name="dns_hexonet"/>
|
||||
|
|
@ -354,7 +355,7 @@ To issue a cert:
|
|||
|
||||
The `Hexonet_Login` and `Hexonet_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
If you find any bugs, please report [here](https://github.com/Neilpang/acme.sh/issues/2389)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2389)
|
||||
|
||||
|
||||
<a name="dns_domeneshop"/>
|
||||
|
|
@ -375,7 +376,7 @@ Ok, let's issue a cert now:
|
|||
|
||||
The `DOMENESHOP_Token` and `DOMENESHOP_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2457)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2457)
|
||||
|
||||
|
||||
<a name="dns_opnsense"/>
|
||||
|
|
@ -401,7 +402,7 @@ Ok, let's issue a cert now:
|
|||
|
||||
The `OPNs_Host`, `OPNs_Port`, `OPNs_Key`, `OPNs_Token` and `OPNs_Api_Insecure` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2480)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2480)
|
||||
|
||||
|
||||
<a name="dns_rcode0"/>
|
||||
|
|
@ -434,7 +435,7 @@ export RCODE0_TTL=60
|
|||
```
|
||||
Use a different TTL for the generated records
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2490)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2490)
|
||||
|
||||
|
||||
<a name="dns_miab"/>
|
||||
|
|
@ -458,7 +459,7 @@ To issue a cert:
|
|||
|
||||
The `MIAB_Username`, `MIAB_Password` and `MIAB_Server` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2550)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2550)
|
||||
|
||||
|
||||
<a name="dns_nic"/>
|
||||
|
|
@ -487,7 +488,7 @@ To issue a cert:
|
|||
|
||||
The `NIC_Username`, `NIC_Password`, `NIC_ClientID` and `NIC_ClientSecret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2547)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2547)
|
||||
|
||||
Docs:
|
||||
* https://www.nic.ru/help/upload/file/API_DNS-hosting-en.pdf
|
||||
|
|
@ -511,7 +512,7 @@ Ok, let's issue a cert now:
|
|||
|
||||
The `LSW_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2558)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2558)
|
||||
|
||||
|
||||
|
||||
|
|
@ -532,7 +533,7 @@ Ok, let's issue a cert now:
|
|||
|
||||
The `VARIOMEDIA_API_TOKEN` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2564)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2564)
|
||||
|
||||
|
||||
<a name="dns_pleskxml"/>
|
||||
|
|
@ -563,8 +564,7 @@ Ok, let's issue a cert now:
|
|||
|
||||
The `pleskxml_uri`, `pleskxml_user` and `pleskxml_pass` will be saved in `~/.acme.sh/account.conf` and reused when needed.
|
||||
|
||||
If you find any bugs, please report here:
|
||||
https://github.com/Neilpang/acme.sh/issues/2577
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2577)
|
||||
|
||||
|
||||
<a name="dns_pdnsmanager"/>
|
||||
|
|
@ -613,6 +613,7 @@ To issue a cert:
|
|||
## 95. Use easyDNS.net API to automatically issue a cert
|
||||
You need to sign up for API access [here](https://cp.easydns.com/manage/security/api/signup.php).
|
||||
Or select 'User' -> 'Security' from the top menu and select 'signup' in the 'easyDNS REST API' section after logging in to your account.
|
||||
|
||||
API Docs: https://sandbox.rest.easydns.net:3001/
|
||||
|
||||
Note that initially you are only granted API access to a sandbox environment, not your live DNS settings.
|
||||
|
|
@ -628,7 +629,7 @@ Ok, let's issue a cert now:
|
|||
```
|
||||
The `EASYDNS_Token` and `EASYDNS_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/acmesh-official/acme.sh/issues/2647)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2647)
|
||||
|
||||
|
||||
<a name="dns_clouddns"/>
|
||||
|
|
@ -648,7 +649,7 @@ Ok, let's issue a cert now:
|
|||
```
|
||||
The `CLOUDDNS_EMAIL`, `CLOUDDNS_PASSWORD` and `CLOUDDNS_CLIENT_ID` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2699)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2699)
|
||||
|
||||
|
||||
<a name="dns_dynv6"/>
|
||||
|
|
@ -670,7 +671,7 @@ To issue a cert use:
|
|||
./acme.sh --issue --dns dns_dynv6 -d example.dynv6.net -d *.example.dynv6.net
|
||||
```
|
||||
|
||||
Report any issues [here](https://github.com/acmesh-official/acme.sh/issues/2702)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2702)
|
||||
|
||||
|
||||
<a name="dns_kas"/>
|
||||
|
|
@ -689,6 +690,7 @@ Now you are able to issue a cert:
|
|||
```
|
||||
The `KAS_Login`, `KAS_Authtype` and `KAS_Authdata` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2715)
|
||||
|
||||
<a name="dns_constellix"/>
|
||||
|
||||
|
|
@ -708,6 +710,7 @@ To issue a cert:
|
|||
|
||||
The `CONSTELLIX_Key` and `CONSTELLIX_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2724)
|
||||
|
||||
<a name="dns_nm"/>
|
||||
|
||||
|
|
@ -748,12 +751,13 @@ To issue a cert:
|
|||
|
||||
The `HostingUkraine_Login` and `HostingUkraine_Token` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2683)
|
||||
|
||||
<a name="dns_arvan"/>
|
||||
|
||||
## 102. Use ArvanCloud domain API
|
||||
|
||||
Get your API token at https://npanel.arvancloud.com/profile/api-keys
|
||||
Get your API token at https://npanel.arvancloud.ir/profile/api-keys
|
||||
|
||||
```sh
|
||||
export Arvan_Token="<token>"
|
||||
|
|
@ -780,7 +784,7 @@ Adding the second record will overwrite the first one.
|
|||
See https://joker.com/faq/content/6/496/en/let_s-encrypt-support.html:
|
||||
> ... this request will replace all TXT records for the specified label by the provided content...
|
||||
|
||||
Report any issues [here](https://github.com/acmesh-official/acme.sh/issues/2840)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2840)
|
||||
|
||||
```sh
|
||||
export JOKER_USERNAME="xxxx"
|
||||
|
|
@ -799,7 +803,7 @@ The `JOKER_USERNAME` and `JOKER_PASSWORD` will be saved in `~/.acme.sh/account.c
|
|||
|
||||
## 104. Use 1984Hosting domain API
|
||||
|
||||
https://1984hosting.com/ does not provide an API to update DNS records
|
||||
https://1984.hosting/ does not provide an API to update DNS records
|
||||
(other than IPv4 and IPv6 dynamic DNS addresses). The `acme.sh` plugin therefore
|
||||
retrieves and updates domain TXT records by logging into the 1984Hosting
|
||||
website to read the HTML and posting updates as HTTP. The plugin needs to
|
||||
|
|
@ -822,14 +826,14 @@ Ok, let's issue a cert now:
|
|||
./acme.sh --issue --dns dns_1984hosting -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any issues [here](https://github.com/Neilpang/acme.sh/issues/2851)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2851)
|
||||
|
||||
|
||||
<a name="dns_aruba"/>
|
||||
|
||||
## 105. Use Aruba domain API
|
||||
|
||||
Get your api token following instruction here at https://admin.arubabusiness.it/DashBoard/WebApiGuide.aspx
|
||||
Get your API token following instruction here at https://admin.arubabusiness.it/DashBoard/WebApiGuide.aspx
|
||||
```sh
|
||||
export ARUBA_TK="<API Token>"
|
||||
export ARUBA_AK="<Username>"
|
||||
|
|
@ -840,7 +844,7 @@ Ok, let's issue a cert now:
|
|||
./acme.sh --issue --dns dns_aruba -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any issues [here](https://github.com/JTrotta/acme.sh/issues)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2994)
|
||||
|
||||
|
||||
<a name="dns_transip"/>
|
||||
|
|
@ -852,7 +856,7 @@ First you need to login to your TransIP account to get your [private key](https:
|
|||
export TRANSIP_Username="MyUserName"
|
||||
export TRANSIP_Key_File="private_key"
|
||||
```
|
||||
Note: TransIP is rather slow, so adding a --dnssleep of 300 might be adviced.
|
||||
Note: TransIP is rather slow, so adding a `--dnssleep` of 300 might be advised.
|
||||
Note 2: if the DNS fails with something like
|
||||
```
|
||||
Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 60
|
||||
|
|
@ -869,8 +873,9 @@ you can add this trusted root CA with
|
|||
--ca-bundle COMODO_RSA_Certification_Authority.crt
|
||||
```
|
||||
|
||||
This script will create a new access token with a default lifetime of 30 minutes. Note that these tokens are by default IP-whitelisted and will not work if your IP is not whitelisted in the Transip control panel.
|
||||
If you cannot work with IP whiltelisting, then make sure you create a key with `Only allow whitelisted IP's` unchecked and set the environment variable as follows:
|
||||
This script will create a new access token with a default lifetime of 30 minutes.
|
||||
Note that these tokens are by default IP-whitelisted and will not work if your IP is not whitelisted in the Transip control panel.
|
||||
If you cannot work with IP whitelisting, then make sure you create a key with `Only allow whitelisted IP's` unchecked and set the environment variable as follows:
|
||||
```sh
|
||||
export TRANSIP_Token_Global_Key="true"
|
||||
```
|
||||
|
|
@ -880,6 +885,7 @@ To issue a cert:
|
|||
./acme.sh --issue --dns dns_transip --dnssleep 300 -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2949)
|
||||
|
||||
<a name="dns_df"/>
|
||||
|
||||
|
|
@ -897,6 +903,7 @@ To issue a cert:
|
|||
|
||||
The `df_user` and `df_password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2897)
|
||||
|
||||
<a name="dns_njalla"/>
|
||||
|
||||
|
|
@ -911,7 +918,7 @@ To issue a cert:
|
|||
./acme.sh --issue --dns dns_njalla -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Please report any bugs here: https://github.com/acmesh-official/acme.sh/issues/2913
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2913)
|
||||
|
||||
|
||||
<a name="dns_vercel"/>
|
||||
|
|
@ -954,13 +961,15 @@ in order to avoid multiple `get_zone_id` requests two months later.
|
|||
> don't forget to change the domain's whois ns section to them and wait about 24-48 Hours.
|
||||
> See [Hetzner wiki](https://docs.hetzner.com/dns-console/dns/general/what-has-changed).
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2943)
|
||||
|
||||
|
||||
<a name="dns_kappernet"/>
|
||||
|
||||
## 111. Use kapper.net DNS API
|
||||
Contact kapper.net support via support@kapper.net to get your kapper.net DNS Panel API Key and Secret.
|
||||
|
||||
For initialzation call following in commandline
|
||||
For initialization call following in commandline
|
||||
```sh
|
||||
export KAPPERNETDNS_Key="yourKAPPERNETapikey"
|
||||
export KAPPERNETDNS_Secret="yourKAPPERNETapisecret"
|
||||
|
|
@ -974,7 +983,9 @@ You can start the acme.sh with following parameters for testing
|
|||
|
||||
Please replace `example.com` with the name of the domain you wish to create a certificate for.
|
||||
|
||||
After the test you can replace your kapper.net DNS Panel API Key and Secret, it is stored in `~/.acme.sh/account.conf`.
|
||||
After the test you can replace your `kapper.net` DNS Panel API Key and Secret, it is stored in `~/.acme.sh/account.conf`.
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2977)
|
||||
|
||||
|
||||
<a name="dns_wedos"/>
|
||||
|
|
@ -1000,6 +1011,8 @@ Issue your certs:
|
|||
|
||||
WEDOS_User and WEDOS_Hash will be stored in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2981)
|
||||
|
||||
|
||||
<a name="dns_shellrent"/>
|
||||
|
||||
|
|
@ -1029,6 +1042,8 @@ Let's issue a cert now:
|
|||
```
|
||||
The SH_Username and SH_Token and SH_Domain_ID will be saved in ~/.acme.sh/account.conf and will be reused when needed.
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2997)
|
||||
|
||||
|
||||
<a name="dns_openstack"/>
|
||||
|
||||
|
|
@ -1041,8 +1056,8 @@ This provider requires the OpenStack Client (python-openstackclient) and
|
|||
Designate client (python-designateclient) be installed and available in your path.
|
||||
|
||||
It also requires you use Keystone V3 credentials, which can be either password or
|
||||
application credentials provided as environment variables. Any other
|
||||
authentication method will not save your credentials for renewal.
|
||||
application credentials provided as environment variables.
|
||||
Any other authentication method will not save your credentials for renewal.
|
||||
|
||||
You will most likely want to source your OpenStack RC file to set your environment variables:
|
||||
|
||||
|
|
@ -1066,7 +1081,7 @@ To issue a cert:
|
|||
|
||||
Your OpenStack credentials will be saved to `~/.acme.sh/account.conf` and reused on renewal.
|
||||
|
||||
Report any issues [here](https://github.com/acmesh-official/acme.sh/issues/3054)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3054)
|
||||
|
||||
|
||||
<a name="dns_netlify"/>
|
||||
|
|
@ -1085,7 +1100,7 @@ Issue a cert with:
|
|||
./acme.sh --issue --dns dns_netlify -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any issues [here](https://github.com/acmesh-official/acme.sh/issues/3088)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3088)
|
||||
|
||||
|
||||
<a name="dns_edgedns"/>
|
||||
|
|
@ -1112,15 +1127,15 @@ To issue a cert:
|
|||
|
||||
Your Akamai Edgegrid credentials will be saved to `~/.acme.sh/account.conf` and reused on renewal.
|
||||
|
||||
Report any issues [here](https://github.com/acmesh-official/acme.sh/issues/3157)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3157)
|
||||
|
||||
|
||||
<a name="dns_wedos"/>
|
||||
|
||||
## 117. Use WEDOS DNS API
|
||||
WEDOS DNS provider from Czech Republic.
|
||||
WEDOS DNS provider from the Czech Republic.
|
||||
DNS API implementation for WEDOS require your WEDOS's account to allow WAPI interface.
|
||||
You have to login to WEDOS administration, in setting allow WAPI interface (in days when this manual were written it was for free completelly).
|
||||
You have to login to WEDOS administration, in setting allow WAPI interface (in days when this manual were written it was for free completely).
|
||||
Configure WAPI interface to XML interface and register the IP addresses (IPv4 and IPv6) of the server where you plan to use acme.sh.
|
||||
That is from the manual side.
|
||||
|
||||
|
|
@ -1137,7 +1152,7 @@ Then you can issue a certificates:
|
|||
./acme.sh --issue --dns dns_wedos -d example.com -d *.examle.com
|
||||
```
|
||||
|
||||
Report any issues [here](https://github.com/acmesh-official/acme.sh/issues/3166).
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3166).
|
||||
|
||||
But before reporting run the acme.sh with `--debug 2` switch and append full acme.sh output to the issue report.
|
||||
|
||||
|
|
@ -1156,7 +1171,7 @@ To issue a cert:
|
|||
./acme.sh --issue --dns dns_websupport -d example.com -d *.examle.com
|
||||
```
|
||||
|
||||
Report any issues [here](https://github.com/akulumbeg/acme.sh/issues)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3486)
|
||||
|
||||
|
||||
<a name="dns_infomaniak"/>
|
||||
|
|
@ -1173,7 +1188,7 @@ export INFOMANIAK_API_TOKEN="<token>"
|
|||
./acme.sh --issue --dns dns_infomaniak -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3188)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3188)
|
||||
|
||||
|
||||
<a name="dns_bookmyname"/>
|
||||
|
|
@ -1190,7 +1205,7 @@ export BOOKMYNAME_PASSWORD="yyy"
|
|||
./acme.sh --issue --dns dns_bookmyname -d example.com -d *.example.com --dnssleep 600
|
||||
```
|
||||
|
||||
Please report any issue to [here](https://github.com/acmesh-official/acme.sh/issues/3209)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3209)
|
||||
|
||||
|
||||
<a name="dns_anx"/>
|
||||
|
|
@ -1206,7 +1221,7 @@ export ANX_Token='<token>'
|
|||
./acme.sh --issue --dns dns_anx -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3238)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3238)
|
||||
|
||||
|
||||
<a name="dns_synology_dsm"/>
|
||||
|
|
@ -1220,7 +1235,7 @@ To issue a cert:
|
|||
```
|
||||
You can find more details [here](https://github.com/arabezar/acme.sh/wiki)
|
||||
|
||||
Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3248)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3248)
|
||||
|
||||
|
||||
<a name="dns_huaweicloud"/>
|
||||
|
|
@ -1241,6 +1256,8 @@ To issue a cert:
|
|||
./acme.sh --issue --dns dns_huaweicloud -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3265)
|
||||
|
||||
|
||||
<a name="dns_simply"/>
|
||||
|
||||
|
|
@ -1273,6 +1290,8 @@ To issue a cert:
|
|||
./acme.sh --issue --dns dns_world4you -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3269)
|
||||
|
||||
|
||||
<a name="dns_scaleway"/>
|
||||
|
||||
|
|
@ -1290,21 +1309,14 @@ To issue a cert run:
|
|||
./acme.sh --issue --dns dns_scaleway -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3295)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3295)
|
||||
|
||||
|
||||
<a name="dns_ls"/>
|
||||
|
||||
## 127 First you need to login to your LS account to get your API Key.
|
||||
## 127. LS
|
||||
|
||||
```sh
|
||||
export LS_Key="<KEY>"
|
||||
```
|
||||
|
||||
Ok, let's issue a cert now:
|
||||
```sh
|
||||
./acme.sh --issue --dns dns_ls -d example.com -d *.example.com
|
||||
```
|
||||
_removed_
|
||||
|
||||
|
||||
<a name="dns_rackcorp"/>
|
||||
|
|
@ -1320,6 +1332,8 @@ To issue a cert:
|
|||
./acme.sh --issue --dns dns_rackcorp -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3351)
|
||||
|
||||
|
||||
<a name="dns_ionos"/>
|
||||
|
||||
|
|
@ -1338,6 +1352,8 @@ To issue a certificate, execute:
|
|||
./acme.sh --issue --dns dns_ionos -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3379)
|
||||
|
||||
|
||||
<a name="dns_porkbun"/>
|
||||
|
||||
|
|
@ -1356,6 +1372,8 @@ To issue a certificate, execute:
|
|||
./acme.sh --issue --dns dns_porkbun -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3450)
|
||||
|
||||
|
||||
<a name="dns_aurora"/>
|
||||
|
||||
|
|
@ -1375,7 +1393,7 @@ To issue a certificate, execute:
|
|||
./acme.sh --issue --dns dns_aurora -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3459)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3459)
|
||||
|
||||
|
||||
<a name="dns_azion"/>
|
||||
|
|
@ -1397,7 +1415,7 @@ To issue a certificate, execute:
|
|||
./acme.sh --issue --dns dns_azion -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3555)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3555)
|
||||
|
||||
|
||||
<a name="dns_oci"/>
|
||||
|
|
@ -1450,7 +1468,7 @@ To issue a cert:
|
|||
|
||||
The `VEESP_User` and `VEESP_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3712)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3712)
|
||||
|
||||
|
||||
<a name="dns_cpanel"/>
|
||||
|
|
@ -1478,11 +1496,11 @@ Ok, let's issue a cert now:
|
|||
./acme.sh --issue --dns dns_cpanel -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
(see https://api.docs.cpanel.net/cpanel/introduction/#cpanel-or-webmail-session-url-1 regarding cPanel ports)
|
||||
See https://api.docs.cpanel.net/cpanel/introduction/#cpanel-or-webmail-session-url-1 regarding cPanel ports.
|
||||
|
||||
The `cPanel_Username`, `cPanel_Apitoken` and `cPanel_Hostname` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3732)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3732)
|
||||
|
||||
|
||||
<a name="dns_ispman"/>
|
||||
|
|
@ -1507,7 +1525,7 @@ Ok, let's issue a cert:
|
|||
./acme.sh --issue --dns dns_ispman -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Please report bugs [here](https://github.com/acmesh-official/acme.sh/issues/3751)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3751)
|
||||
|
||||
|
||||
<a name="dns_dnshome"/>
|
||||
|
|
@ -1526,7 +1544,7 @@ Ok, let's issue a cert now:
|
|||
|
||||
The `DNSHOME_Subdomain` and `DNSHOME_SubdomainPassword` will be saved in the domain conf and will be reused when needed.
|
||||
|
||||
Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3819)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3819)
|
||||
|
||||
|
||||
<a name="dns_mythic_beasts"/>
|
||||
|
|
@ -1547,7 +1565,7 @@ Ok, let's issue a cert now:
|
|||
|
||||
The credentials will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3848)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3848)
|
||||
|
||||
|
||||
|
||||
|
|
@ -1577,6 +1595,8 @@ To avoid such timing errors the `--dnssleep` flag can be set to a value of 240 s
|
|||
./acme.sh --issue --dns dns_sdns -d example.com -d *.example.com --dnssleep 240
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3917)
|
||||
|
||||
|
||||
<a name="dns_udr"/>
|
||||
|
||||
|
|
@ -1599,6 +1619,8 @@ To issue a certificate, execute:
|
|||
|
||||
The `UDR_USER` and `UDR_PASS` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3923)
|
||||
|
||||
|
||||
<a name="dns_curanet"/>
|
||||
|
||||
|
|
@ -1619,6 +1641,8 @@ To issue a certificate, execute:
|
|||
|
||||
The `CURANET_AUTHCLIENTID` and `CURANET_AUTHSECRET` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3933)
|
||||
|
||||
|
||||
<a name="dns_artfiles"/>
|
||||
|
||||
|
|
@ -1642,7 +1666,7 @@ To issue a certificate, execute:
|
|||
./acme.sh --issue --dns dns_artfiles -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Please report any issue [here](https://github.com/Eagle3386/acme.sh/issues)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4718)
|
||||
|
||||
|
||||
<a name="dns_geoscaling"/>
|
||||
|
|
@ -1666,7 +1690,7 @@ To issue a certificate, execute:
|
|||
|
||||
The `GEOSCALING_Username` and `GEOSCALING_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report bugs [here](https://github.com/acmesh-official/acme.sh/issues/3969)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3969)
|
||||
|
||||
|
||||
<a name="dns_fornex"/>
|
||||
|
|
@ -1685,6 +1709,8 @@ To issue a cert, run command:
|
|||
./acme.sh --issue --dns dns_fornex -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/3998)
|
||||
|
||||
|
||||
<a name="dns_dnsservices"/>
|
||||
|
||||
|
|
@ -1701,6 +1727,8 @@ To issue a cert, run command:
|
|||
./acme.sh --issue --dns dns_dnsservices -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4152)
|
||||
|
||||
|
||||
<a name="dns_nodion"/>
|
||||
|
||||
|
|
@ -1719,6 +1747,8 @@ To issue a certificate, execute:
|
|||
acme.sh --issue --dns dns_nodion -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4157)
|
||||
|
||||
|
||||
<a name="dns_la"/>
|
||||
|
||||
|
|
@ -1736,6 +1766,8 @@ To issue a cert, run command:
|
|||
./acme.sh --issue --dns dns_la -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4257)
|
||||
|
||||
|
||||
<a name="dns_yc"/>
|
||||
|
||||
|
|
@ -1766,6 +1798,8 @@ Now you can issue a cert:
|
|||
|
||||
Both, `YC_Folder_ID`, `YC_SA_ID`, `YC_SA_Key_ID`, `YC_SA_Key_File_PEM_b64` or `YC_SA_Key_File_Path` and `YC_Zone_ID` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4210)
|
||||
|
||||
|
||||
<a name="dns_bunny"/>
|
||||
|
||||
|
|
@ -1785,7 +1819,7 @@ Then you can issue a cert:
|
|||
|
||||
The `BUNNY_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
If you find any bugs with the Bunny DNS API integration, please report them here: https://github.com/Neilpang/acme.sh/issues/4296
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4296)
|
||||
|
||||
|
||||
<a name="dns_selfhost"/>
|
||||
|
|
@ -1810,6 +1844,8 @@ export SELFHOSTDNS_MAP="_acme-challenge.example.com:12345:98765 alias.example.co
|
|||
acme.sh --issue --dns dns_selfhost -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4291)
|
||||
|
||||
|
||||
<a name="dns_rage4"/>
|
||||
|
||||
|
|
@ -1828,6 +1864,8 @@ To issue a cert, run command:
|
|||
./acme.sh --issue --dns dns_rage4 -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4306)
|
||||
|
||||
|
||||
<a name="dns_gcore"/>
|
||||
|
||||
|
|
@ -1845,6 +1883,8 @@ To issue a cert, run command:
|
|||
./acme.sh --issue --dns dns_gcore -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4460)
|
||||
|
||||
|
||||
<a name="dns_dynadot"/>
|
||||
|
||||
|
|
@ -1871,6 +1911,8 @@ DYNADOTAPI_RETRY_SLEEP=30
|
|||
* `DYNADOTAPI_API_RETRIES` number of times to attempt a DYNADOT api call.
|
||||
* `DYNADOTAPI_RETRY_SLEEP` sleep time between DYNADOT api calls (only applied if a call fails and DYNADOTAPI_API_RETRIES is set great than 1)
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4523)
|
||||
|
||||
|
||||
<a name="dns_ipv64"/>
|
||||
|
||||
|
|
@ -1888,6 +1930,8 @@ To issue a cert, run command:
|
|||
./acme.sh --issue --dns dns_ipv64 -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4419)
|
||||
|
||||
|
||||
<a name="dns_nanelo"/>
|
||||
|
||||
|
|
@ -1906,7 +1950,7 @@ To issue a cert, run the following command:
|
|||
./acme.sh --issue --dns dns_nanelo -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
Please report any bugs/issues [here](https://github.com/acmesh-official/acme.sh/issues/4519)
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4519)
|
||||
|
||||
|
||||
<a name="dns_googledomains"/>
|
||||
|
|
@ -1932,14 +1976,15 @@ The script tries to infer the zone registered with Google Domains by matching th
|
|||
export GOOGLEDOMAINS_ZONE="google-domains-zone"
|
||||
```
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4545)
|
||||
|
||||
|
||||
<a name="dns_dnsexit"/>
|
||||
|
||||
## 158. Use DNSExit API to automatically issue cert
|
||||
|
||||
|
||||
You'll need an API key for your DNSExit account which you can find under your Account Profile. You will also need your account login (username and password).
|
||||
You'll need an API key for your DNSExit account which you can find under your Account Profile.
|
||||
You will also need your account login (username and password).
|
||||
|
||||
```sh
|
||||
export DNSEXIT_API_KEY="<Your API key>"
|
||||
|
|
@ -1952,12 +1997,9 @@ To issue a cert, run the following:
|
|||
./acme.sh --issue --dns dns_dnsexit -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
The login variables will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
|
||||
|
||||
The login variables will be saved in ~/.acme.sh/account.conf and will be reused when needed.
|
||||
|
||||
Please report any bugs/issues [here](https://github.com/acmesh-official/acme.sh/issues/4719).
|
||||
|
||||
|
||||
Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/4719).
|
||||
|
||||
|
||||
<a name="dns_myapi"/>
|
||||
|
|
@ -1966,7 +2008,7 @@ Please report any bugs/issues [here](https://github.com/acmesh-official/acme.sh/
|
|||
|
||||
If your API is not supported yet, you can write your own DNS API.
|
||||
|
||||
Let's assume you want to name it 'myapi':
|
||||
Let's assume you want to name it `myapi`:
|
||||
|
||||
1. Create a bash script named `~/.acme.sh/dns_myapi.sh`,
|
||||
2. In the script you must have a function named `dns_myapi_add()` which will be called by acme.sh to add the DNS records.
|
||||
|
|
@ -1976,16 +2018,16 @@ Let's assume you want to name it 'myapi':
|
|||
./acme.sh --issue --dns dns_myapi -d example.com -d *.example.com
|
||||
```
|
||||
|
||||
For more details, please check our sample script: [dns_myapi.sh](https://github.com/Neilpang/acme.sh/blob/master/dnsapi/dns_myapi.sh)
|
||||
For more details, please check our sample script: [dns_myapi.sh](https://github.com/acmesh-official/acme.sh/blob/master/dnsapi/dns_myapi.sh)
|
||||
|
||||
See: [DNS API Dev Guide](https://github.com/Neilpang/acme.sh/wiki/DNS-API-Dev-Guide)
|
||||
See: [DNS API Dev Guide](https://github.com/acmesh-official/acme.sh/wiki/DNS-API-Dev-Guide)
|
||||
|
||||
|
||||
<a name="dns_lexicon"/>
|
||||
|
||||
## Use lexicon DNS API
|
||||
|
||||
[How to use lexicon DNS API](https://github.com/Neilpang/acme.sh/wiki/How-to-use-lexicon-DNS-API)
|
||||
[How to use lexicon DNS API](https://github.com/acmesh-official/acme.sh/wiki/How-to-use-lexicon-DNS-API)
|
||||
|
||||
-----------------------------------
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue