You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched other issues and found no duplicates
I want to report a bug and not ask a question
Operating system type
Windows
CPU architecture
AMD64
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
107.18
Description
What did you do?
Blocked Apple tracking / ad domains in HOSTS file via Spybot Anti-Beacon
Expected result
Domain should be blocked, rewritten to 0.0.0.0
Actual result
In latest version of AdGuard 107.18, it blocks (rewrites) the domain once, then resolves the domain and lets data through immediately afterwards, according to the logs.
Screenshots (if applicable)
Additional information
OS is Windows Server 2008 R2 (up to date with final patches)
If you look at the request types, it's processing HTTPS queries, not IP records. These will not resolve to an IP for the purposes of connecting to the server in question. In that sense, there's nothing to rewrite/block. Only A and AAAA record lookups need rewriting to 0.0.0.0 here, which prevents your client(s) from connecting to the domain in question. The HTTPS lookup is simply asking for information about the domain. See here.
RainmakerRaw is correct. We currently only rewrite A and AAAA records for system /etc/hosts files. You can add this file as a separate filtering rule list instead, which will block all types of queries.
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question
Operating system type
Windows
CPU architecture
AMD64
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
107.18
Description
What did you do?
Blocked Apple tracking / ad domains in HOSTS file via Spybot Anti-Beacon
Expected result
Domain should be blocked, rewritten to 0.0.0.0
Actual result
In latest version of AdGuard 107.18, it blocks (rewrites) the domain once, then resolves the domain and lets data through immediately afterwards, according to the logs.
Screenshots (if applicable)
Additional information
OS is Windows Server 2008 R2 (up to date with final patches)
HOSTS data from Spybot Anti-Beacon:
The text was updated successfully, but these errors were encountered: