homelab/traefik
1
0
Fork 0
Code Activity

Support custom DNS resolvers for Let's Encrypt.

Browse source
This commit is contained in:
Ludovic Fernandez 2018-10-25 17:38:04 +02:00 • committed by Traefiker Bot
parent ac11323fdd
commit 74dc5b1c58
5 changed files with 113 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

21
docs/configuration/acme.md
View file

@ -142,6 +142,23 @@ entryPoint = "https"
#
# delayBeforeCheck = 0
# Use following DNS servers to resolve the FQDN authority.
#
# Optional
# Default: empty
#
# resolvers = ["1.1.1.1:53", "8.8.8.8:53"]
# Disable the DNS propagation checks before notifying ACME that the DNS challenge is ready.
#
# NOT RECOMMENDED:
# Increase the risk of reaching Let's Encrypt's rate limits.
#
# Optional
# Default: false
#
# disablePropagationCheck = true
# Domains list.
# Only domains defined here can generate wildcard certificates.
# The certificates for these domains are negotiated at traefik startup only.
@ -302,6 +319,10 @@ Here is a list of supported `provider`s, that can automate the DNS verification,
| [VegaDNS](https://github.com/shupp/VegaDNS-API) | `vegadns` | `SECRET_VEGADNS_KEY`, `SECRET_VEGADNS_SECRET`, `VEGADNS_URL` | Not tested yet |
| [VULTR](https://www.vultr.com) | `vultr` | `VULTR_API_KEY` | Not tested yet |
#### `resolvers`
Use custom DNS servers to resolve the FQDN authority.
### `domains`
You can provide SANs (alternative domains) to each main domain.