Add support for blocked replies with NOERROR code and empty answer - #8245
Open
agross wants to merge 1 commit into
Open
Add support for blocked replies with NOERROR code and empty answer#8245agross wants to merge 1 commit into
agross wants to merge 1 commit into
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.
agross
force-pushed
the
fix-8024
branch
2 times, most recently
from
March 5, 2026 00:37
4deb43d to
f53fdba
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
3 times, most recently
from
March 12, 2026 04:57
8793a81 to
524f303
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
3 times, most recently
from
March 21, 2026 04:47
3d04800 to
2576ed7
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
5 times, most recently
from
April 2, 2026 05:14
63d944c to
3c7d59d
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
6 times, most recently
from
April 11, 2026 05:04
791c59e to
d303033
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
4 times, most recently
from
April 18, 2026 05:17
a6a6155 to
d1cec80
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
3 times, most recently
from
April 25, 2026 05:22
de66c70 to
7098c29
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
from
May 23, 2026 06:19
9fa908a to
b302afb
Compare
|
Hi and thanks @agross , I hope this request gets merged. |
github-actions
Bot
force-pushed
the
fix-8024
branch
3 times, most recently
from
June 3, 2026 08:28
bd3ba4e to
acfe573
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
2 times, most recently
from
June 10, 2026 07:17
0d0fbf2 to
61d4ded
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
2 times, most recently
from
June 23, 2026 06:58
8acc6e3 to
fad2f82
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
4 times, most recently
from
July 3, 2026 06:42
eb21ce2 to
83a4842
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
2 times, most recently
from
July 9, 2026 06:54
c3dce85 to
55e2fa5
Compare
agross
force-pushed
the
fix-8024
branch
2 times, most recently
from
July 11, 2026 09:02
a03dc9d to
e584b53
Compare
Author
|
5 months later, and not a single reply from the team. Is this of no interest, @KirillCAdGuard, @kpokas-adguard, @AleksandrKalininAdGuard? |
github-actions
Bot
force-pushed
the
fix-8024
branch
from
July 17, 2026 17:35
e584b53 to
fb1cc0a
Compare
Author
github-actions
Bot
force-pushed
the
fix-8024
branch
5 times, most recently
from
July 28, 2026 06:05
1afb685 to
b372707
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
2 times, most recently
from
July 31, 2026 06:26
95aa855 to
4d25df9
Compare
github-actions
Bot
force-pushed
the
fix-8024
branch
from
August 1, 2026 06:11
4d25df9 to
3bf55c9
Compare
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