SOA for authoritative NXDOMAIN response should be in the Authoritative section #151
Conversation
This file contains 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
… to go in the Authoritative section, not the Answer section. This fixes the acme-dns validation for the lego Let's Encrypt client.
|
Thanks a bunch! Almost is definitely not enough :) |
jacobmyers-codeninja
pushed a commit
to jacobmyers-codeninja/acme-dns
that referenced
this pull request
Sep 30, 2020
… to go in (joohoi#151) the Authoritative section, not the Answer section. This fixes the acme-dns validation for the lego Let's Encrypt client.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When appending the SOA for authoritative NXDOMAIN responses, it needs to go in the Authoritative section, not the Answer section.
This fixes acme-dns validation for the lego Let's Encrypt client.
This issue was identified in lego issue 707 and almost fixed in acme-dns issue 127.