mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
HTTPS record filtering #4623
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#4623
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ExternalDatabase on GitHub (Jul 28, 2023).
Originally assigned to: @Mizzick on GitHub.
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 or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
FreeBSD, AMD64 (aka x86_64)
Installation
Docker
Setup
On one machine
AdGuard Home version
v0.107.35
Action
/opt/adguardhome/work # nslookup -debug -type=a 'meetings.hubspot.com' '192.168.0.94'
Server: 192.168.0.94
Address: 192.168.0.94:53
Query #0 completed in 4ms:
Non-authoritative answer:
Name: meetings.hubspot.com
Address: 0.0.0.0
Expected result
return 0.0.0.0 or NXDOMAIN
AND
don't ask upstream server
Actual result
returned 4 times 0.0.0.0 and 1 time the request has been passed to upstream DNS server
that domain is just an example - it happens for other domains too randomly
most requests of blocked domains are resolved as 0.0.0.0 locally and AGH doesn't ask upstream for resolve them
Additional information and/or screenshots
From AGH:

From upstream DNS server:

@fernvenue commented on GitHub (Jul 29, 2023):
So what is your block rule for this domain?
@ExternalDatabase commented on GitHub (Jul 29, 2023):
that domain is listed within StevenBlack/hosts, so it should be blocked
in AGH settings blocking mode is set to return 0.0.0.0 (Null IP)
when the Client asks AGH for that domain type 'A' record - it is blocked
when the Client asks AGH for that domain type 'https' record - AGH resolve it as normal (not listed) domain
SOA, CNAME, NS, TXT requests are processed too (answer blocked by the upstream dns server):
`/opt/adguardhome/work # nslookup -debug -type=soa 'meetings.hubspot.com' '192.168.0.94'
Server: 192.168.0.94
Address: 192.168.0.94:53
Query #0 completed in 21ms:
Non-authoritative answer:
/opt/adguardhome/work # nslookup -debug -type=ns 'meetings.hubspot.com' '192.168.0.94'
Server: 192.168.0.94
Address: 192.168.0.94:53
Query #0 completed in 25ms:
Non-authoritative answer:
/opt/adguardhome/work # nslookup -debug -type=cname 'meetings.hubspot.com' '192.168.0.94'
Server: 192.168.0.94
Address: 192.168.0.94:53
Query #0 completed in 19ms:
Non-authoritative answer:
/opt/adguardhome/work # nslookup -debug -type=txt 'meetings.hubspot.com' '192.168.0.94'
Server: 192.168.0.94
Address: 192.168.0.94:53
Query #0 completed in 21ms:
Non-authoritative answer:
`
@fernvenue commented on GitHub (Jul 29, 2023):
That's why I asked for your block rules, and you said:
Actually this is a duplicate issue for https://github.com/AdguardTeam/AdGuardHome/issues/5124, as @RainmakerRaw said:
So AdGuardHome's behavior here is actually expected and there is no error, and you can add this file as a separate filtering rule list instead, which will block all types of queries.
@ainar-g commented on GitHub (Jul 31, 2023):
Safari is starting to use the
ipv[46]hintsfor DNS resolving, though, so I feel like we should handle these better.@Mizzick, please add DNS HTTPS record filtering to AdGuard Home.
@Mizzick commented on GitHub (Aug 9, 2023):
Please have a look, we have implemented the requested changes.
The new build version
v0.108.0-a.646+1e939703has been just published to the edge channel.@ainar-g commented on GitHub (Aug 21, 2023):
We'll close this issue. Feel free to reopen if the filtering doesn't work for you.