Add SUBNET option to Unbound port to enable EDNS Client Subnet Support #438
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
Author
|
Should add that most other platforms have this enabled by default, and that no actual changes should be observed, as the relevant options are disabled by default. The module-config change should just enable support, but not change resolving behaviour as per unbound module docs. |
|
Any possibility to add these in the near future? |
|
Any info these request? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This just adds support for EDNS Client Subnet in Unbound, as that feature has been requested for a while and the relevant issue has been stale. Any comments are welcome. An option in the UI can be added at a later time, although I will give that a shot as well.
Fixes: #363