From 52b32edfd2c8a610c928b216bbf95c6abe390cfc Mon Sep 17 00:00:00 2001
From: Terry Kerr <root@oefd.ca>
Date: Wed, 28 Nov 2018 17:35:48 -0500
Subject: [PATCH] add dns_vultr info to READMEs

---
 README.md        |  1 +
 dnsapi/README.md | 18 ++++++++++++++++++
 2 files changed, 19 insertions(+)

diff --git a/README.md b/README.md
index c4ea5c6e..c54b0568 100644
--- a/README.md
+++ b/README.md
@@ -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: 
 
diff --git a/dnsapi/README.md b/dnsapi/README.md
index bb0e89d0..1cb6ab97 100644
--- a/dnsapi/README.md
+++ b/dnsapi/README.md
@@ -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.