docker-pihole-unbound VS nextdns

I'm running the chriscrowe 'one container' build for pihole for ad-blocking (https://github.com/chriscrowe/docker-pihole-unbound), and unbound for private recursive DNS which is running great on my Zima board.

I believe my problem stems from when I tried to install the pihole-unbound container (https://github.com/chriscrowe/docker-pihole-unbound)

I've got lucky enough that I could get in Nov-19 a Raspberry Pi 4 with 4GB of RAM that I use as a NAS+Pi-Hole + Unbound +Other stuff (running Void MUSL of course) and instead of an SD I use an HDD for the OS + a 5TB HDD for the data and even fully loaded all cores it barely consumes more than 22W.

I was only able to get pihole macvlan approach working with an ssh access + docker-compose approach. I used the crowe one-container approach Still had to enable Open vSwitch for the network in Synology first.

You can follow the doc to do those install steps within your own Dockerfile. Or you can use the commonly recommended chriscrowe image, which does what I’m describing.

When I started experimenting with this topic chriscrowe's was a baseline for stuff that I tryed out, so kudos to chris!

It seems you’re looking at a wrong file. Here is a docker file for one-container solution: https://github.com/chriscrowe/docker-pihole-unbound/blob/55c88afaf8d76958923adc38f4c12a80e1cb9084/one-container/pihole-unbound/Dockerfile

2) you can use something like this maintained GitHub repo. Just decide if you want to use 1 or 2 containers and modify the ip and gateways, etc accordingly.

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