Add hickory server roles with example configurations #3
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
* split installation into its own chapter * add boxes to highlight notes or important information * expand recursive resolver page
|
Pinging @bluejekyll, as I'm unable to select a reviewer. |
bluejekyll
approved these changes
Nov 19, 2024
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.
This expands the book with examples on how to run Hickory as an authoritative name server and recursive resolver, including DNSSEC validation. The associated steps and configurations are explained. Example queries provide more information how these roles work, what they return as responses etc. A introductory chapter explains the installation process of Hickory.
The PR is currently in draft mode, to get feedback and to wait until a new tagged release of
hickory-dnsis available on crates.io. The information will be updated accordingly to use this release then.See #2