hosts VS nextdns

Not by default but a blocklist can be found here https://github.com/StevenBlack/hosts

While it is now unblocked, the Steven Black list has been blocking a lot of innocent CDNs.

jQuery: https://github.com/StevenBlack/hosts/issues/2520

How does this compare to using a hosts file with known ad servers?

like: https://github.com/StevenBlack/hosts

I use the Hosts file to block a ton of ads and that works really well. https://github.com/StevenBlack/hosts Something worth considering if your ad blocker isn't working well.

The no-tracking project used by RaspAP is shutting down, so we took the opportunity to search for open source blocklist alternatives. Among the best is Steven Black's hosts list: https://github.com/StevenBlack/hosts

No idea, api.radar.io is on the block list since January 2020.

The commit's comment is "major update from adaway.org"

https://github.com/stevenblack/hosts/commit/4fa0470

You can also use a declarative adblocker like uBlock Origin Lite [1], which only provides the browser with a list of elements to filter, but doesn't have any permissions to read content or perform requests. Or simply use your hosts file to apply OS-wide filtering with no browser add-ons needed: https://github.com/StevenBlack/hosts

Be aware that if you use these "passive" blocking methods, there are some sites like YouTube where you will see ads, because in these cases it's necessary to actually manipulate page content to hide them. What you can do is use a traditional adblocker but enable it only for these few sites where the declarative approach is not enough, take a look at [2] for more details.

[1] https://github.com/uBlockOrigin/uBOL-home

[2] https://seirdy.one/posts/2022/06/04/layered-content-blocking...

https://github.com/StevenBlack/hosts if you want to do it on your PC.

When I select my custom hosts file, it basically breaks internet. However, if I choose a custom hosts file that is a copy of the dev's default, or if I just add a few lines to it, it will work. If I add too many lines, or use a different hosts file altogether (like the ones recommended by the dev), all connectivity breaks. Of course the latest official LetMeBlock is installed and mDNSResponder killed/restarted. I'm using Dopamine on A12+.

Block 45.76.93.104 and 2001:19f0:6c00:1b0e:5400:4ff:fecd:7828 at the firewall if possible.

Ensure that DNS-over-HTTP (DoH) is enabled where it can be.

Set upstream DNS servers that block malware, such as 1.1.1.2 or NextDNS

Delete "fritz.box" from the domain search list in DNS settings.

Educate your parents to be cautious about directly typing domain names or searching from the OmniBox.

https://nextdns.io/

https://blog.cloudflare.com/introducing-1-1-1-1-for-families...

I've tried hosted Pi-Hole and AdGuard Home. They are good as long as I'm around to fix stuffs. Then I tested something which can be global (home) and also for individual devices -- Control-D, NextDNS, and Adguard DNS. All of them works pretty well. If I really have to choose, then it would be in the order of NextDNS > Control-D > AdGuard DNS. Affiliated with none, and have decided to subscribe to all three to further test them for this year.

https://controld.com

https://nextdns.io

https://adguard-dns.io

Okay but NextDNS' own homepage says it "blocks ads and trackers on websites and in apps" - https://nextdns.io

I first used Safari on Windows around 2006. Put me off forever.

You just need Firefox and the extensions that mean ads are never seen.

That said, take a look at https://nextdns.io

just run snort and get nextdns.io account and use those DNS servers to control your DNS.

I'm using NextDNS which can be integrated into TailScale MagicDNS. It works seamlessly. You may need to pay if you have a high usage rate. I pay for the Pro version but that's less than $30 CAD a year. I did have in house Raspberry PI and Pi-Hole DNS but it was a lot of work.

pretty much to the same effect of a pihole, yet you can get up and running in minutes. You can then configure wherever you please: your browser, your laptop, your phone, or even your router.

[0]: https://nextdns.io