Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
General Apps
AdGuard
Help needed with DNS configuration
Message
<blockquote data-quote="Brahman" data-source="post: 1093675" data-attributes="member: 11847"><p>Do not set DOH in your bowser. DNS over Https means all your DNS queries gets encrypted and sends to the preferred dns resolver via port 443. If you set doh in browser, no dns queries go to your router, all your router sees is "the encrypted traffic over port 443" and nothing else. So in such case no filtering takes place, which defeats your intended purpose of using adgurd plugin. Instead create a rule in opnsens to route all TCP and UDP traffic in port 53 ( all unencrypted dns queries comes through this port)to your adguard listening port. </p><p>You do not need nextdns with your setup, you can add as many blocklist to your adguard ( but the less is better) server and get the same protection as nextdns provides.</p></blockquote><p></p>
[QUOTE="Brahman, post: 1093675, member: 11847"] Do not set DOH in your bowser. DNS over Https means all your DNS queries gets encrypted and sends to the preferred dns resolver via port 443. If you set doh in browser, no dns queries go to your router, all your router sees is "the encrypted traffic over port 443" and nothing else. So in such case no filtering takes place, which defeats your intended purpose of using adgurd plugin. Instead create a rule in opnsens to route all TCP and UDP traffic in port 53 ( all unencrypted dns queries comes through this port)to your adguard listening port. You do not need nextdns with your setup, you can add as many blocklist to your adguard ( but the less is better) server and get the same protection as nextdns provides. [/QUOTE]
Insert quotes…
Verification
Post reply
Top