Ultimate.Hosts.Blacklist VS Pi-hole

https://github.com/Ultimate-Hosts-Blacklist/Ultimate.Hosts.B...

Don't forget about hosts.deny (but you probably need it at your router if you are behind one).

You might also look into HOSTS file editors and lists of servers to block. HOSTS is a single file you can edit on a Windows machine using a standard text editor. I used to follow this closely so I don't have a recommendation on which list to use, but here's a possible starting point: https://github.com/Ultimate-Hosts-Blacklist/Ultimate.Hosts.Blacklist

I think the main source I use that doesn't seem to be in rethinkDNS is the Ultimate Hosts Blacklist's hosts and/or hosts.deny files.

So it presumably has the same function as a hosts file. You can find examples like this which is portable to any Linux (or Windows) installation.

Here's an additional 630k+ blocks for you. Super easy to use. https://github.com/Ultimate-Hosts-Blacklist/Ultimate.Hosts.Blacklist

Downloads and stores hosts blacklist as a part of the environment

One thing I can suggest that will ALWAYS work is blocking known ad websites on host file level: https://github.com/Ultimate-Hosts-Blacklist/Ultimate.Hosts.Blacklist (or equivalent, there's a lot of resources for it if you look it up)

Si te preguntas, ¿por qué no usar Adguard o Pihole? 🤔

This is an overreaction, almost to the point of absurdity.

Risks inherent to pipe installers are well understood by many. Using your logic, we should abandon Homebrew [1] (>38k stars on GitHub), PiHole [2] (>46k stars on GitHub), Chef [3], RVM [4], and countless other open source projects that use one-step automated installers (by piping to bash).

A more reasonable response would be to coordinate with the developers to update the docs to provide alternative installation methods, rather than throwing the baby out with the bathwater.

[1] https://brew.sh/

[2] https://github.com/pi-hole/pi-hole

[3] https://docs.chef.io/chef_install_script/#run-the-install-sc...

[4] https://rvm.io/rvm/install

Pi-hole to block ads and tracking for my less technically savvy relatives

https://pi-hole.net/

I ran a competing project[0] on my home network for a few years before I discovered NextDNS[1]. What I lost in performance (requests don't leave my house) I gained in portability: ALL my devices can take advantage – at home and away – and time-saved. PiHole works 90% of the time, but when it did stop working, I'd have to spend a bit of time fixing it. At $20/year, I simply couldn't compete with NextDNS.

Note: This isn't a shill for NextDNS; I love these kinds of projects and think they absolutely should exist, but NextDNS just happens to be one of those dead-simple SaaS tools that is an insanely good value.

0 - https://pi-hole.net/

1 - https://nextdns.io

It definitely IS an option, but at the network level.

https://pi-hole.net/

It runs on damn near everything, and is a DNS level adblocker for the whole network.

I recently switched to Wipr [0]. It’s dead simple to use, and will auto update its filter lists in the background.

Adguard [1] is a decent free option.

I also use a Pi-hole [2] on my network.

[0] https://kaylees.site/wipr.html

[1] https://adguard.com/en/adguard-safari/overview.html

[2] https://pi-hole.net/

Are you trying to build a DNS proxy (similar to Pi-hole) that intercepts DNS requests and checks for the ones that look harmful? If so, I would suggest trying to separately build a DNS client and a DNS server, before trying to integrate them together. Start with Beej's Guide to Network Programming if you need to learn the basics of sockets, and then take a look at the documents that define the DNS protocol itself (RFC1034 and RFC1035).

Setup a pi-hole.

It's definitely not as simple as installing an app on your phone, but I run a Pi-hole on my home network, and it does block ads in many games.