New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set up Pi Hole on Docker #472
Comments
If its only for Smart Home Devices, maybe setting up Whitelist might be easier then a large blacklist. Just means everything is blocked expect for the addresses allowed. This will use less processing power on the pihole as well |
That's a Great Idea @AaronArgent! Maybe I'll flip flop the idea then. Have the DHCP and IOT whitelist on the weaker Pi Zero and the Block list on a Docker VM. |
Raspian 9 is no longer supported. Time to move the Pi to Docker for easy updating. |
So the Raspberry Pi died.. Brought up a new PiHole on Docker now. This will make things a LOT easier and easier to backup now. |
Run two pi-holes on the network in the typical DNS load balanced fashion.
I would run one on a physical Pi Zero and the other in a docker container. The first would be the primary DNS and single DHCP for the network. It would also have a less aggressive set of lists for blocking and would be used for most of the user devices on the network (phones, laptops, etc…) while the second could have a much more aggressive set of blocking rules that I would point only Smart Home devices to. Since they are less likely to need to get to most websites (or ANY), I could be extremely aggressive on the blocking. Also since that Pi-Hole would be on the docker image, it would have more horsepower and could handle a larger block list. I would then just hardcode that Pi-hole address into the DNS sections of the IOT devices.
The text was updated successfully, but these errors were encountered: