ervin/acme.sh
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

add dns_vultr info to READMEs

Browse Source
This commit is contained in:
Terry Kerr 2018-11-28 17:35:48 -05:00
parent 2db2d4028e
commit 52b32edfd2
2 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -329,6 +329,7 @@ You don't have to do anything manually!
1. Namecheap API (https://www.namecheap.com/)
1. MyDNS.JP API (https://www.mydns.jp/)
1. hosting.de (https://www.hosting.de)
1. Vultr API (native) (https://www.vultr.com)
And:

18
dnsapi/README.md
View File

@ -1054,6 +1054,24 @@ acme.sh --issue --dns dns_hostingde -d example.com -d *.example.com
The hosting.de API key and endpoint will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
## 56. Use Vultr API
You'll need an API key for your Vultr account which you can find [under the Account settings](https://my.vultr.com/settings/#settingsapi) and you'll want to ensure the API key is allowed for any IPs you might be using acme.sh with.
Vultr supports creating sub-accounts with limited permissions, and it's a good idea to create a sub-account with only the 'Manage DNS' permission and use an API key from that sub-account.
```sh
export VULTR_API_KEY="<Your API key>"
```
To issue a cert:
```sh
acme.sh --issue --dns dns_vultr -d example.com -d www.example.com
```
The `VULTR_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
# Use custom API
If your API is not supported yet, you can write your own DNS API.