Skip to content
April 20, 2019

Setting up Pi-hole

Blocking all ads in my local network

Pi-hole has been on my radar for quite some time. After being overwhelmed by the ads on my mobile, I decided to give it a go. Essentially it blocks all ads on the DNS level.

For our computers, it's easy to set up an adblocker. It will be annoying in some browsers like Safari but that's ok.

What about a smart-TV though? How can one ensure that their purchase is ad-free? The fact that this is even reality is audacious, but let it be for now. We want to verify that our TVs are full of corny sitcoms and nothing else. In the case of mobiles, even if we can run adblocker (for example Firefox mobile) we can't take the performance hit.

Reading from their website...

The Pi-holeĀ® is a DNS sinkhole that protects your devices from unwanted content, without installing any client-side software.

  • Easy-to-install: our versatile installer walks you through the process, and takes less than ten minutes
  • Resolute: content is blocked in non-browser locations, such as ad-laden mobile apps and smart TVs
  • Responsive: seamlessly speeds up the feel of everyday browsing by caching DNS queries
  • Lightweight: runs smoothly with minimal hardware and software requirements
  • Robust: a command line interface that is quality assured for interoperability
  • Insightful: a beautiful responsive Web Interface dashboard to view and control your Pi-hole
  • Versatile: can optionally function as a DHCP server, ensuring all your devices are protected automatically
  • Scalable: capable of handling hundreds of millions of queries when installed on server-grade hardware
  • Modern: blocks ads over both IPv4 and IPv6
  • Free: open source software which helps ensure you are the sole person in control of your privacy


My collegue Chris has written a great tutorial using balena. In my version, I'll use Rasbian instead.

  • Raspberry Pi ('B' in my case)

  • SD card (I use a leftover SanDisk extreme 64GB)

  • Ethernet cable

  • Raspberry power adaptor

  • Etcher (In order to flash the Rasbian image)

  • Raspbian Stretch Lite

  • Your favorite SSH client (I'll use macOS terminal)

Preparing the Raspberry Pi

First of all, let's get the Raspbian Lite image, and then Etcher in order to flash it.


If you're an owner of a MacBook Pro with two USB-C ports like me, get your dongles ready.


When the flashing is complete, we have to enable SSH on the device. That's very simple, as we only have to create an 'shh' file in the root directory.

# 'cd' in /Volumes/{name-of-the-media}
touch ssh

Great, now let's get these two lovebirds together, and plug the Pi in the router. My spare Raspberry had a Sense HAT attached. In due time, I'm hoping to add a proper case and work on some cable management (soonTM). I decided to use Ethernet, as I want it to be a reliable middleman.



Nothing out of order here


Preparing the installation

Cool beans, now we need to get the IP address of the Pi. Simply log in to your router's admin panel and check the connected devices.


Alright, let's SSH into our Rasbian image pi@{ip-of-the-device}. The password is raspberry (use passwd to change it).

Before we continue, let's bring our image up to date

sudo apt-get update
sudo apt-get dist-upgrade


and then run the install command

curl -sSL | bash


and you will see this lovely image. The pink screen of progress.


Really now it's up to you. Follow along with the wizard, and pick whatever suits your use case. When everything is said and done, we can go check the dashboard!

Remember to change the password before quitting the terminal session with pihole -a -p




I love this already. I'm a sucker for graphs, even if I don't understand a thing.

Let's get some extra lists from blocklist


and place them in Settings/Blocklists.


I've also scanned through Reddit and played around with various others like:



  • Make sure you have a static IP for the Raspberry Pi. Modern routers are smart enough to assign the same IP, but let's be extra careful.
  • My Pi stopped working for a bit. I imagine that's because my power adaptor isn't the native one, but the first Samsung charger I had lying around. In that case, setting two instances of Pi-hole can help.
  • There's a catch-all solution. As you noticed we have to be up-to-date with the block lists. For smart TVs with 0 protection that's good enough. But for your other devices, if you can add another level of protection like Little Snitch that would be great.

Moving on

Well now, it's up to both of us to use it more. I'm sure there must be some false positives, so with everyday use, these issues should be ironed out.

I'll keep the Pi as my DNS server for my own laptop & mobile, but let my work-related one talk with the router directly. Better not mess with meetings for such an experiment :)


I'm not a clever man, I used this guide and the dedicated subreddit for help.