dns: support additional section and SRV/TXT queries#29
Open
erikrk wants to merge 1 commit into
Open
Conversation
When responding to a PTR query, SRV and TXT records should be placed in the additional section and not the answer section. When responding to an A or AAAA query, addresses of mismatching type should be placed in the additional section and not the answer section. Respond to SRV and TXT queries. Only respond to PTR queries without instance specified (instance is not included in name of PTR records). PTR/SRV/TXT responses are always forced to yield predictable results. Rate limiting is only kept for the legacy ANY query handling. Fix a bug where the timeout was updated even if the response is forced and potential NULL pointer issues. Signed-off-by: Erik Karlsson <erik.karlsson@iopsys.eu>
|
mark |
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
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.
When responding to a PTR query, SRV and TXT records should be placed in the additional section and not the answer section. When responding to an A or AAAA query, addresses of mismatching type should be placed in the additional section and not the answer section.
Respond to SRV and TXT queries. Only respond to PTR queries without instance specified (instance is not included in name of PTR records). PTR/SRV/TXT responses are always forced to yield predictable results. Rate limiting is only kept for the legacy ANY query handling.
Fix a bug where the timeout was updated even if the response is forced and potential NULL pointer issues.