Fix typo in multiple DNS challenge provider warning #11001
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix the result of "Multiple DNS Challenge" section example.
kevinpollet
changed the title
rtribotte
added
area/documentation
status/3-needs-merge
and removed
status/2-needs-review
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Fix the result of "Multiple DNS Challenge" section example.
What does this PR do?
Adjusts documentation regarding Multiple DNS Challenge.
Motivation
Currently, the documentation states that
_acme-challenge.example.orgCNAME'd tochallenge.example.comwill allow to issue certificate forexample.comhaving access only toexample.org, which is, I believe, is the other way around¹: the confirmation of theexample.orgdomain control is being delegated with the CNAME toexample.comwhere DNS TXT record can be manipulated.More
Additional Notes
¹ https://letsencrypt.org/docs/challenge-types/