Add the ability to use multiple DNS providers in parallel #2028
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This provider simply chains multiple providers together so that
if you're using more than one DNS service, it will validate ACME
with both. This solves the problem of updating only one provider
and having Let's Encrypt or whomever query the other one, leading
to a long wait time for verification if it even happens at all.
This type of config is common when DNS is maintained as text
files in repos with tools like DNSControl or OctoDNS for High
Availability in case one DNS provider goes down.
Tested with the CLI client:
related to #1342