-
Notifications
You must be signed in to change notification settings - Fork 257
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
Blocking DNS requests by type #384
Comments
Hi, our approach is the following: dnsproxy is just a DNS forwarder and we intend to keep it this way. |
But you are already blocking the "ANY" type, I just ask you to expand the list. Blocking just two types AAAA and Type65 reduces unnecessary requests by 66% and increases responsiveness without using the large adguardhome package. dnsproxy is used much more often than adguardhome. #[feature request] |
Well, Anyways, I'd say the real feature request here is moving the filtering features from AdGuard Home to dnsproxy. Maybe at some point we'll decide to change the current approach, but at the moment duplicating functionality seems like an overkill. Why wouldn't you use AGH instead of dnsproxy? It can be configured to work as a pure no-UI DNS filtering solution. |
Merge in GO/dnsproxy from AGDNS-2622-fix-race to master Squashed commit of the following: commit 59243bc Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Fri Dec 20 20:20:37 2024 +0300 all: imp code commit c222940 Author: Stanislav Chzhen <s.chzhen@adguard.com> Date: Fri Dec 20 19:00:49 2024 +0300 all: fix race
Thanks for the software, it's the best!
Please add a function for blocking DNS requests by type. DNS blocking type 65 (https) is very necessary.
analog ||*^$dnstype=HTTPS adguard home
The text was updated successfully, but these errors were encountered: