Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upSupport DS record delegation for subzone #249
Open
Conversation
It looks like DS records are part of the DNSSEC bits of DNS, https://www.godaddy.com/help/what-is-a-ds-record-6148. There's a bit of discussion and background on why octoDNS doesn't support DNSSEC over in #176. It'd be nice if it octoDNS had support, but a quick look though things at that point seemed to indicate that provider support wasn't really there/ready for it. |
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.
nunnun commentedJun 20, 2018
Currently delegating a NS record to subzone is allowed.
But I think DS record is also needed for subzone delegation.
So I've changed the code to allow a DS record as well as a NS record.