Client-based filtering settings do not work when filtering is turned off in the general settings

[ZeroClover]

Prerequisites

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

Issue Details

• Version of AdGuard Home server:
  v0.105.2
• How did you install AdGuard Home:
  Snapcraft
• How did you setup DNS configuration:
  Dedicated server
• CPU architecture:
  AMD64
• Operating system and version:
  Debian 10

---

I set up a new instance of AGH and want to disable filtering by default and enable it only for specific clients.

I disabled Filter in the general settings of AGH, then added a client with the name ADfilter and set the Identifier to adfilter and enabled filtering for this client.

Screenshot:

After that, I tried DNS queries through DoH (https://example.com/dns-query/adfilter) and DoT (tls://adfilter.example.com), and the ad domain resolves normally and is not filtered.

Screenshot:

[ainar-g]

Thanks for the report. As far as I know, it “works as intended”, although I personally am not sure if that's what we want to go on doing. @ameshkov, what would you say?

[ameshkov]

@ainar-g actually, this looks like a bug to me.

[ZeroClover]

@ainar-g actually, this looks like a bug to me.

Does this mean that client-level filtering should remain in effect when global filtering settings are turned off?

Will AdGuard fix this?

Thanks.

[ainar-g]

@ameshkov, I've seen the code that does this, so I just assumed that that was the correct behaviour. If it is a bug, I'll see if I can fix it in the current cycle.

[ameshkov]

@ainar-g well, note that I am talking about the global setting (settings -> general -> block domains using filters), not the "Disable/enable protection" button on the main screen.

[noyyyy]

I have faced the same issue and hope it to be fixed