Support for an additional EDNS client subnet for AAAA queries #21
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.
It is useful on dual-stack connections with mixed AS-Numbers to specify both an IPv4 and IPv6 EDNS client subnet and use the IPv6 client subnet when asking for AAAA records. In that case, you would put your IPv4 subnet into
-gdns:edns
and your IPv6 subnet into-gdns:edns6
I am not sure how useful this will be for most users, but it has advantages in my setup. I would like to hear feedback or please feel free to close/ignore this pull request if it is beyond dingos scope.