In this guide, I will walkthrough how to install and test the pi-hole on Ubuntu and more specifically, Ubuntu Server. These same instructions may work on Ubuntu Desktop, but I strongly suggest Server. Why Ubuntu instead of a Raspberry Pi? I love Raspberry Pis and I probably own at least 10 of them. But sometimes I want to perform DNS blocking/blackholing and I either a) don’t have a Raspberry Pi in an environment or b) I have a virtual environment where I can add some robustness to the solution. At the time of this writing, I should mention that pi-hole is currently *not* supported on Ubuntu 18.04 LTS. Instead, the project officially supports 16.04 LTS. So why install it on 18.04? Ubuntu 16.04 LTS will only receive updates/support until April 2021 unless you purchase extended security maintenance (ESM). I install systems with the intention to not make significant changes to them for some time and the end of life for 16.04 is less than that window of time. ?

24July2018 – Originally posted
1Sept2018 – Added steps to fix 18.04.1
29Nov2018 – Verified as working
26Jan2019 – Verified as working on both 18.04 and 18.04.1
16Feb2019 – Verified on 18.04.2. Additional steps for 18.04.1 are not required.
5Apr2020 – Verified as working on 18.04.4. Added section on removing

Why remove advertising?

Advertising is great because it pays content creators for their work. After all, even this site utilizes Google Ads. So why would I create a write-up on blocking ads? Because advertisements are known to carry malicious payloads and it’s impossible to distinguish what’s good and what’s bad. As a result, blocking advertising has become an absolute necessity for those who are security conscious. On a personal note, I’ll happily sacrifice some advertising income for the sake of readers/everyone improving their security! As many have figured out, a side benefit of blocking ads is a better user experience and a substantial drop in bandwidth usage. I’ve written several walkthroughs on how to block ads using different devices such as pfBlockerNG on pfSense. If you own a pfSense, I would strongly suggest using the aforementioned guide to create an experience very similar to the pi-hole. Using pfBlockerNG on pfSense has quite a few additional features such as IP blocking and quite honestly, there is no need to add yet another system to manage.

Install Ubuntu

Installing Ubuntu server is ridiculously easy. Simply download the latest Ubuntu Server LTS ISO and install it as you would any standard OS. Note: There is a slight difference in the install steps if you are installing 18.04.1 LTS instead of 18.04 (even if 18.04 is upgraded to 18.04.1). I explain where the 2 install paths diverge in the Ubuntu 18.04.1 LTS section below. You can safely use the defaults throughout the installation, although I would install security updates automatically when given the option. You may also need to install SSH if that is how you plan to access and manage your server remotely (other than the web interface). If you are installing this in a virtual/VMware environment for a fairly small number of devices, I would recommend a 1GB of memory, 1 CPU core, and at least 30GB of hard drive. FWIW, the initial install of Ubuntu and pi-hole (before any logs) is under 5GB of disk space so 30GB should give you some room to grow. You could potentially require more resources if you have a lot of devices or those devices make a ton of DNS requests. That is something you will need to keep an eye on after you get it up and running!

pi-hole Minimum Requirements
CPUMemoryHard Drive
1 core1 GB (or 2GB)30 GB

Update Ubuntu

After your Ubuntu system finishes the install and reboots, login via an SSH terminal or from the console. You should be greeted with a welcome screen similar to the one below with the exception your package and security update counts may be different.


Welcome to Ubuntu 18.04 LTS

* Documentation:
* Management:
* Support:

113 packages can be updated.
51 updates are security updates.


Once you are logged in and sitting at a terminal prompt, run package updates manually using the command below. Note the command will do the repository update, upgrade the packages, and then reboot in one fell swoop. Grab your favorite beverage and let that process run its course.

$ sudo apt-get update && sudo apt-get upgrade -y && sudo reboot

After the system updates and reboots, log back in via SSH or the console. As you will see on your own install, the packages and security updates should both be at zero (or really close).


Welcome to Ubuntu 18.04 LTS

* Documentation:
* Management:
* Support:

0 packages can be updated.
0 updates are security updates.


Ubuntu 18.04.1 LTS only

There is a slight difference with the installed base packages between an Ubuntu 18.04 install upgraded to 18.04.1 and a straight 18.04.1 install. Interestingly enough, these additional steps are not necessary for 18.04.2 or later either. The package differences cause the 18.04.1 install to drop back down to a command line (as show below) during install of pi-hole.

Pi-Hole crash to command line

The way to correct this issue is in the gray box below. Basically, you add ‘universe’ to the ‘bionic main’ repo line in the /etc/apt/sources.list using the sed command. You follow that with an apt-get update and then install the missing packages. Shout out to xkeyscore_ on Reddit for finding the missing dependencies.

Note: the instructions below are only for the 18.04.1 download. If you installed 18.04 and upgraded to 18.04.1, do NOT run the commands below or you will break your install!!! If you are running 18.04.2 or later, do NOT run these commands!

– /etc/apt/sources.list –
deb bionic main -> deb bionic main universe

$ sudo cp /etc/apt/sources.list /etc/apt/sources.list.orig
$ sudo sed -i 's/bionic main/bionic main universe/g' /etc/apt/sources.list
$ sudo apt-get update
$ sudo apt-get --no-install-recommends install dialog dhcpcd5

If you’re unable to run the last command to install the packages, try the command below and then retry the one above. You do not need to run this command if your apt-get install ran correctly. 

sudo dpkg --configure -a

Install pi-hole

Now it’s time to run the pi-hole install script so just copy/paste the command in the gray box below. Yes, it is a single-lined command. That said, this is extremely dangerous if you are unsure of the source. I would recommend taking a peek at the code before you run it. This is easily done considering the address simply re-directs to “” script on a GitHub repo. If you can’t read code, that’s ok… At the very least, look at the repo and see if the script has changed recently. If it has, you might consider waiting a few days or at least snoop around some forums to make sure the changes were “expected.”

$ curl -sSL | bash

Assuming you ran the command above as a standard user instead of root (or with sudo), you will get prompted for the user password again.

[✗] Root user check
[i] Script called with non-root privileges
The Pi-hole requires elevated privileges to install and run
Please check the installer for any concerns regarding this requirement
Make sure to download this script from a trusted source

[✓] Sudo utility check
[sudo] password for pihole:
[✓] Root user check

For the most part, you can select the defaults or simply hit “Ok” on most of the screens, however, I want to highlight a few items/recommendations. First, the pi-hole project is donation-based. Be sure to visit their donation page and keep the project going!

During the install, the pi-hole points out it is currently using a DHCP address instead of a static IP address. As stated in the picture below, using a static IP address is highly, highly recommended. Don’t forget that in most cases, you do not want your new static IP address in your current DHCP range. Instead, assign your pi-hole an IP address outside of your current DHCP pool. For instance, if your DHCP pool is then you could safely assign your pi-hole (assuming that IP address wasn’t already used).

Static IP address vs. DHCP address

I was an early adopter of Quad9 and I’m still very bullish on them. I’ve written several articles about Quad9 and configuring it on numerous devices. Long story short, Quad9 provides another layer of protection and that’s a good thing! For that reason, I would suggest selecting ‘Quad9 (filtered + ECS)’ as the upstream DNS provider when asked during the pi-hole install.


If you are curious about the different Quad9 options available, here you go. ‘Quad9 (filtered, DNSSEC)’ means we want to block malicious domains and we are protecting against forged DNS records by using DNSSEC. This option is tied to the Quad9 namesake – ‘Quad9 (unfiltered, no DNSSEC)’, which is actually, means that we will *not* block malicious domains and we will *not* use DNSSEC. Last, we have ‘Quad 9 (filtered + ECS)’. Filtered is familiar, but what is ECS? ECS, also known as EDNS client subnet, is generally used to help speed up data from content delivery networks.  Although not stated in the pi-hole menu, this option is based on According to Quad9, this IP address supports all of the above — DNS encryption, DNSSEC, EDNS Client Subnet, and blocking malicious domains.

When asked which blacklists to use, make sure you de-select ‘’ or you will receive an error when it attempts to download the file (below). You’ll also receive several ongoing errors because the list is no longer supported. If you accidentally added it and now you’re getting errors, refer to the section below on Removing (ad_servers.txt).

[i] Target: (ad_servers.txt)
[✗] Status: Not found
[✗] List download failed: no cached list available

The install will download At the installation complete screen, you should take note of your IP address (if you changed it) and also the randomly generated password. Beware of ones that look like lowercase l’s and zeros that look like uppercase O’s. If you can copy and paste it, I would strongly suggest it to avoid issues logging in! You can change the pi-hole web password as described in the section below.

Take note of the IP address and password

Change your pi-hole web password

Via the an SSH terminal or the console, type in “pihole -a -p” and hit enter. Type in your new password twice.

$ pihole -a -p
Enter New Password (Blank for no password):
Confirm Password:
[✓] New password set

pi-hole web interface

The pi-hole has a very friendly web interface to manage your device. Using your web browser, go to http://<ip address>/admin and you should see a nice statistics screen as shown below. Click on ‘Login’ and either type in the password provided to you during install (or the password you changed to in the last section).

pi-hole first login

After you get some clients configured (described below), you can come back to the web admin interface and see how many domains are blocked along with quite a few other stats. The web interface is also where you can add other blacklists, whitelist domains, etc.

Statistics on pi-hole install

How it works – testing from the command line

The easiest way to test whether your pi-hole is going to work is via a command line. I would strongly recommend testing before making the DHCP server or client changes below!

We can use the nslookup command from any machine on the network. The format of the nslookup command is the same whether on Linux or Windows — nslookup <hostname to test> <IP address for your pi-hole>. In my test environment, the pi-hole is and we are testing a well-known Yahoo advertising domain, Instead of returning the actual IP address for, the pi-hole returns This effectively blackholes the hostname via DNS so your system/browser is not able to access it. Note: the pi-hole used to use its own IP address, but this caused a slight timeout whereas causes the connection to get dropped immediately.

Server: pihole


If we test against a domain that is not blocked, then we receive the actual external IP addresses for the hostname as shown below.

Server: pihole

Non-authoritative answer:

Client configuration changes

This part of the walkthrough will vary wildly because it changes from one environment to the next. If you can make a change at whatever device or server is handing out DHCP addresses (as shown in the Linksys picture below), then you should absolutely make the change there.

Note: If your system already resolved a domain name, then you may need to clear your local DNS cache, your browser cache, or both. To clear your machine’s cache, from a command line on Windows, type in ‘ipconfig /flushdns’ and that should take care of it. You can run a similar command on a Linux system, although the commands can vary from one installation to the next. More often than not, simply restarting your network interface will work; on most distributions, ‘service networking restart’ or ‘systemctl restart network’ should take care of it for you. Each browser has a slightly different way to clear the cache, however, all of them allow you to pull a new version of the website if you hold down “Shift” while clicking on the refresh/reload button.

router firewall dns change

If you can’t make the change at the server or router/firewall for whatever reason, then you may need to make the change at each client. Changing each client is an issue if you have a number of IoT devices where you can’t even access the underlying configuration. If you have a number of devices, this would also be extremely cumbersome and quite honestly, it might be worth looking at swapping out equipment. Alternatively, you could also disable the current DHCP server entirely and instead enable the DHCP server on the pi-hole (also via the web interface). If you go the pi-hole DHCP server route, make sure you disable the other DHCP server so you don’t have two servers on the same network.

If the client is the route you want to go and I haven’t talked you out of it… On Windows, go to control panel and drill into your network adapter settings as shown below.

pi-hole Windows DNS settings changes

Testing By Browsing

So what does the finished product look like? On many sites like YouTube, you’ll see empty space or a gray box where an ad normally would have been. A browser add-on like uBlock Origin (discussed below) further cleans this up by removing the gray box entirely and it also provides some secondary protections. If you visit (why? seriously, find a new news site), our pi-hole configuration eliminates the wasteland of ads that you normally see as well (red box below). Many sites will look similar to this with vast regions of white space where ads normally would show and don’t be surprised to find ads intermingled with news on many sites. <- In advertising, it’s all about improving that click through ratio (CTR)!

Browsing Yahoo with pi-hole

Removing (ad_servers.txt) appears to be gone for good despite its popularity. Malwarebytes, in their infinite wisdom have discontinued its support. Meanwhile, they are continuing to dissolve any shred of value their brand has/had. At any rate, to remove the from your blocklists, log into your pi-hole, then go to Settings -> Blocklists. De-select the checkbox next to and then click ‘Save and Update’.

Cloud-Lösungen und mobile Mitarbeiter Warum sind mobile Mitarbeiter eine Cyber-Bedrohung?

Telearbeit und Homeoffice sind seit mehr als einem Jahrzehnt auf dem Vormarsch. Laut Bitkom-Studie bietet mittlerweile jedes dritte Unternehmen seinen Mitarbeitern die Möglichkeit zur Arbeit von zuhause aus an – Tendenz steigend.

Ein flexibler Arbeitsplatz bietet mehrere Vorteile – das schwache Glied ist dabei jedoch die Cloud-Sicherheit, die Unternehmen gefährden kann. Laut dem Netwrix Cloud Data Security Report 2019 verzeichneten 38 Prozent der Unternehmen, die mobile Mitarbeiter beschäftigen, Verstöße gegen die Cloud-Datensicherheit. Damit liegt die Zahl doppelt so hoch wie bei eher traditionellen Unternehmen, die nur Mitarbeiter am Standort beschäftigen.

Wer ist ein mobiler Mitarbeiter?

Der Begriff mobile Mitarbeiter ist nicht auf Selbständige und Auftragnehmer beschränkt. Heutzutage arbeiten manche Mitarbeiter jeden Tag von zu Hause oder einem anderen Ort aus und melden sich gelegentlich, wenn nötig, im Unternehmensnetzwerk an (zum Beispiel während einer Geschäftsreise oder an einem Krankheitstag).

Warum stellen mobile Mitarbeiter eine Cyber-Bedrohung dar?

Mobile Mitarbeiter melden sich in ihrem Unternehmensnetzwerk häufig von ihren eigenen Geräten aus an, die mit hoher Wahrscheinlichkeit Sicherheitslücken aufweisen. Beispielsweise ist es kaum oder gar nicht möglich zu gewährleisten, dass diese Geräte frei von schädlicher Software sind und ordnungsgemäß gepatcht wurden. Darüber hinaus können Unternehmen weniger schnell reagieren, wenn ein mobiler Nutzer einen Fehler macht, der zu unbefugtem Datenzugriff oder sogar zu Datenkompromittierungen führt. Solche Fehler sind zu teuer, als dass man sie ignorieren könnte: Die 2019 vom Ponemon Institute durchgeführte Studie „Cost of Data Breach“ ergab, dass 24 Prozent aller Datenverletzungen auf menschliches Versagen zurückzuführen sind, wobei die Gesamtkosten eines Datenverstoßes circa 120 Euro pro Datensatz betragen. Zu den Kosten zählen sowohl direkte finanzielle Auswirkungen (beispielsweise Geldstrafen bei Compliance-Verstößen und Rechtsstreitigkeiten) als auch indirekte Kosten, die durch eine Reputationsschäden verursacht werden, zum Beispiel durch den Verlust der Kundenbindung und des Markenwerts.

Wie können Sie diese Bedrohungen minimieren?

Die ordnungsgemäße Führung mobiler Mitarbeiter ist unmöglich, wenn nicht genau bekannt ist, was diese in der Cloud-Umgebung des Unternehmens tun. Insbesondere ist ein tiefer Einblick in die Nutzeraktivitäten und in die Firmendaten erforderlich.

Einblick in Nutzeraktivitäten

Durch den Einblick, wer was wo und wann tut, kann verdächtiges Verhalten schnell erkannt werden. Zudem kann die IT-Sicherheit rechtzeitig reagieren, bevor es zum Datenverstoß kommt. Darüber hinaus können Vorfälle gründlich untersucht werden, um zu gewährleisten, dass sie nicht noch einmal auftreten. Ein weiterer Vorteil ist, dass Prüfern auf Nachfrage ein Nachweis der Einhaltung gesetzlicher Vorschriften vorgelegt werden kann. Viele Unternehmen haben immer noch nicht genügend Einblick in die Nutzeraktivitäten: 59 Prozent der von Netwrix befragten Unternehmen, die mobile Mitarbeiter beschäftigen, waren nicht in der Lage, die Bedrohungsakteure hinter den Sicherheitsvorfällen in der Cloud zu ermitteln.

Mit einer Softwarelösung, die eine kontinuierliche Überwachung der Nutzeraktivitäten sowie Echtzeitwarnungen bietet, können Sicherheitsverantwortliche Bedrohungen sofort erkennen, detaillierte Untersuchungen durchführen und Compliance-Audits bestehen.

Einblick in Daten

Mit der Cloud ist das Teilen von Daten leichter denn je. Wenn genau ist, welche Daten vorhanden sind, wo sie sich befinden, welche Daten am vertraulichsten sind und wer Zugriff darauf hat, können die Sicherheitsmaßnahmen sich auf die kritischsten oder vertraulichsten Informationen, wie personenbezogene Daten von Kunden und Mitarbeitern, konzentrieren. Wenn nicht bekannt ist, wo sich vertrauliche Daten befinden, ist es unmöglich, sich mit bewährten Sicherheitsmethoden und entsprechend gesetzlicher Bestimmungen entsprechend schützen.

Mithilfe einer Datenerkennungs- und -klassifizierungslösung können Unternehmen ihre vertraulichen Daten lokalisieren und die entsprechenden Kontrollen anwenden. Wer all seine Daten klassifiziert, erlebt mit einer 5-mal geringeren Wahrscheinlichkeit einen Datenverstoß als diejenigen, die darauf verzichten.

Darüber hinaus ist mithilfe der Erkennung und Klassifizierung von Daten möglich, redundante, obsolete und triviale Daten (ROT) identifizieren. Durch die Bereinigung werden die Kosten für die Datenverwaltung und -speicherung gesenkt und die Produktivität gesteigert, da die Benutzer die benötigten Informationen leichter finden können.

Wie kann Sichtbarkeit das Geschäft ankurbeln?

Der Einblick in ihre Cloud-Umgebungen bietet Unternehmen auch langfristig enorme Vorteile. Zunächst kann das Engagement für den Datenschutz unter Beweis gestellt werden, sobald sie in der Lage sind, die persönlichen Daten ihrer Kunden sicher zu speichern und auf das Verlangen, vergessen zu werden, umgehend zu reagieren. Die daraus resultierende Kundenbindung ist ein klarer Wettbewerbsvorteil.

Durch den Einblick in die Daten und die damit zusammenhängenden Nutzeraktivitäten kann man außerdem den Zeit- und Ressourcenaufwand für die Compliance minimieren und hohe Bußgelder vermeiden. Laut einer Studie von Precise Security, beliefen sich Jahr 2019 sich die Strafen, die im Zuge der DSGVO gezahlt werden mussten, auf insgesamt über 402 Millionen Euro, wobei die höchste Strafzahlung in Deutschland bei der Deutschen Wohnen mit 14,5 Millionen Euro lag. Unternehmen sollten deshalb sicherstellen, dass ihre Daten in der Cloud zu jeder Zeit richtig klassifiziert und vor unberechtigtem Zugriff geschützt sind.

Über den Autor: Jürgen Venhorst ist Country Manager DACH bei Netwrix.