Skip to content

AdGuardHome blocked_hosts ignores AdBlock exception rules — any single disallow 'drops' all, making exceptions ineffective #7764

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
4 tasks done
candybars1 opened this issue Apr 13, 2025 · 0 comments

Comments

@candybars1
Copy link

Prerequisites

Platform (OS and CPU architecture)

Linux, ARMv7

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.107.59

Action

I’m encountering an issue with the Disallowed Domains feature (blocked_hosts) in AdGuard Home. According

I’m encountering an issue with the Disallowed Domains feature (blocked_hosts) in AdGuard Home. It seems that when using AdBlock rules, any attempt to block domains results in all domains being dropped. For example, using

 ||*^ 

in blocked_hosts drops everything, and adding exceptions like:

@@||google.com^$important

doesn’t work. this would cause every single domain query to timeout and be dropped. .

Similarly if I:

||com^

all .com domains get dropped, and those queers time out as well.

Other Ad Block based rules also do not work, including regular express expressions and anything else I tried, whether using the UI or AdGuardHome.yaml

The only distinction it seems to make is between Prefix || which is a complete and utter drop of any expression following, which does not apply when using @@||, which is useless since without disallow/drop there is no relevance to overriding "allow.

This behavior is unexpected and not documented. I’m seeking a solution where only specified domains are allowed, while others are dropped without sending default blocked responses.

Steps to Reproduce:
1. Use ||*^ in blocked_hosts to block all domains.
2. Add @@||google.com^$important as an exception.
3. Observe that no domains are allowed.###

Expected result

Expected Behavior:

Exceptions should be respected, allowing specified domains to resolve.

Actual Behavior:

All domains are dropped, regardless of exceptions.

Thank you for looking into this.

“Since version 0.107.x, blocked_hosts supports AdBlock syntax for filtering rules. Errors might not reflect in the UI, but the feature is fully supported.”

Actual result

---@macbooks-MacBook-Pro ~ % dig google.com

; <<>> DiG 9.10.6 <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached

Image
Image
Image

Additional information and/or screenshots

verified on two separate raspberry pi 3b and and AdGuard Home windows as a service installation with various adblock type rules including regix to no avail

@candybars1 candybars1 changed the title Title: Issue with Disallowed Domains (blocked_hosts) Not Respecting Exceptions in AdGuard Home AdGuardHome blocked_hosts ignores AdBlock exception rules — any single disallow 'drops' all, making exceptions ineffective Apr 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant