![]() ![]() One complication - it doesn't deal well with IPv6 enabled and I managed to go around in default configuration. USB 2.0 mode is enough and may prevent eventual 2.4GHz radio interference (may be an issue on some router models). ![]() Instead of USB stick I would use a small SSD in USB enclosure. It's light enough for router use (1GB RAM models at least), the WebUI is nice and informative, the blocklists are fail-safe, there are services blocking options (I was blocking iCloud Private Relay and it works), Cloudflare can provide additional filtering (1.1.1.2/1.0.0.2 servers) and is fast in many locations, DNS traffic is mixed with common https on port 443, 1.1.1.1/help is showing the encryption method correctly. TERMINAL LINUX (USING NEXTDNS WITH ADGUARD DNS LIST nslookup Īddress: nslookup can tell what I liked recently and why - AdGuard Home with DoH to Cloudflare with AdGuard standard ads and security blocklists only. TERMINAL LINUX (USING ADGUARD nslookup Īddress: nslookup Please, see this particularity of the AdguardDNS list, because if not, many domains that should be blocked, will not be using NextDNS with adguard dns list. They use this type of approach in 244 domains, such as: I went to test it in the linux terminal and realized that this type of approach works when using their own DNS ( ), but testing NextDNS with the AdguardDNS list, these domains are not being blocked. You can see that instead of them blocking and probably to save space in the list and make it smaller or to cover possible new tracking domains of the same company, they (Adguard team) block some domains in a single line and put an asterisk * on the domain itself. I went to test blocking two Amazon telemetry domains used on the Echo Show and Fire TV. I just discovered a bug testing NextDNS with AdguardDNS list. Hello, I noticed that NextDNS has a bug related to some domains on the AdguardDNS list. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |