Ad Blocking
I finally set up my Pi-hole DNS sinkhole and couldn’t be happier.
Set-up is straight forward:
- Set-up Raspberry Pi with Raspbian
- ssh with default credentials
- Set-up Pi-Hole
In case you can’t hard wire your Raspberry Pi, see below for /etc/wpa_supplicant/wpa_supplicant.conf
to connect to wifi:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=840
network={
ssid="myWifi"
psk="myPass"
}
A misconception is the you need an Raspberry Pi to run pihole, but there’s also a docker image that can be used in lieu of physical hardware.
There’s also been problems when using pihole with Android devices on the Pi-hole forums (1) (2). The prevailing theory is that there’s probably hard-coded values for Google’s Public DNS. So when an app reports that part of it fails to load (like ads) it defaults to the Public DNS. But an easy fix is to just have your router use the Pi-hole as it’s DNS server. It also has the added benefit that any device on your network will automatically use the Pi-hole, without needing configurations.