Add support for blocked replies with NOERROR code and empty answer#8245
Open
agross wants to merge 1 commit intoAdguardTeam:masterfrom
Open
Add support for blocked replies with NOERROR code and empty answer#8245agross wants to merge 1 commit intoAdguardTeam:masterfrom
agross wants to merge 1 commit intoAdguardTeam:masterfrom
Conversation
| filtering.BlockingModeDefault, | ||
| filtering.BlockingModeNXDOMAIN, | ||
| filtering.BlockingModeREFUSED, | ||
| filtering.BlockingModeNOERROR, |
There was a problem hiding this comment.
The PR adds filtering.BlockingModeNOERROR to the list of valid blocking modes, but I don't see a corresponding implementation in the filtering package. Make sure this mode is properly implemented in the filtering package to handle blocked domains with NOERROR responses without answer sections.
Author
There was a problem hiding this comment.
This is a new approach to responding to filtered queries, not a new method for filtering.
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
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.
Hello,
I'm not a Go developer by trade and not a DNS expert; please be gentle.
I found #8024 is affecting me.
The default behavior of returning the null address makes localhost reachable under blocked names. This causes errors and unwanted behavior, like being able to ping blocked hosts (by talking to localhost).
Returning NXDOMAIN or REFUSED, on the other hand, will cause extra DNS queries with the search domain appended, i.e.,
blocked.example.combecomesblocked.example.com.local.domain.com.By returning NOERROR without an answer section, these problems go away.
With this patch, AdGuard will return a response similar to resolving a non-existing name, i.e., asking a question but not getting an answer:
If NOERROR is selected and a blocked name is requested, it looks like this:
Closes #8024