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
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
Adguard vs NextDNS. Need help understanding the testresults.
Message
<blockquote data-quote="Brahman" data-source="post: 902352" data-attributes="member: 11847"><p>The best option, if you are concerned about dns leaks /port 53 traffic is to use a router that supports either DNS over TLS or DNS over HTTPS. The advantage of such a system is that the router can intercept all port 53 traffic from any connected device to your desired Encrypted dns provider. Windows leaks some port 53 traffic while start up to the router even if you use adguard on desktop or yogadns app. You can not prevent it until you use a router based doh or dnscrypt(simple dns crypt- that sets ipv4 dns to 127.0.0.1 and ipv6 to ::1 a non existence loopback address so that nothing(port 53) goes out and the dnscrypt service then listens to that address-127.0.0.1) So my advice is to</p><p>1. Use <a href="https://yogadns.com" target="_blank">Yoga dns</a> as a frontend to your Nextdns.</p><p>2. use <a href="https://simplednscrypt.org" target="_blank">simple dnscrypt</a>.</p><p>3. You can also use New desktop adguard (Version7.5) and use nextdns as a doh/Dot resolver. (Go to Settings> Dns> Add a custom dns "<a href="https://dns.nextdns.io/xxxxxx" target="_blank">https://dns.nextdns.io/xxxxxx</a>" Replace "xxxxxx" with your configuration id which you can find in your nextdns account).</p><p>4. Since you have disabled IPv6, you dont need to do this. (Go to Control panel> Network and sharing center> Click on ethernet/wifi> Properties> Internet protocol version 6> use the following dns address and paste this " ::1 " without inverted commas. This will prevent dns leaking to ipv6 dns servers.)</p></blockquote><p></p>
[QUOTE="Brahman, post: 902352, member: 11847"] The best option, if you are concerned about dns leaks /port 53 traffic is to use a router that supports either DNS over TLS or DNS over HTTPS. The advantage of such a system is that the router can intercept all port 53 traffic from any connected device to your desired Encrypted dns provider. Windows leaks some port 53 traffic while start up to the router even if you use adguard on desktop or yogadns app. You can not prevent it until you use a router based doh or dnscrypt(simple dns crypt- that sets ipv4 dns to 127.0.0.1 and ipv6 to ::1 a non existence loopback address so that nothing(port 53) goes out and the dnscrypt service then listens to that address-127.0.0.1) So my advice is to 1. Use [URL='https://yogadns.com']Yoga dns[/URL] as a frontend to your Nextdns. 2. use [URL='https://simplednscrypt.org']simple dnscrypt[/URL]. 3. You can also use New desktop adguard (Version7.5) and use nextdns as a doh/Dot resolver. (Go to Settings> Dns> Add a custom dns "[URL]https://dns.nextdns.io/xxxxxx[/URL]" Replace "xxxxxx" with your configuration id which you can find in your nextdns account). 4. Since you have disabled IPv6, you dont need to do this. (Go to Control panel> Network and sharing center> Click on ethernet/wifi> Properties> Internet protocol version 6> use the following dns address and paste this " ::1 " without inverted commas. This will prevent dns leaking to ipv6 dns servers.) [/QUOTE]
Insert quotes…
Verification
Post reply
Top