Our intelligent installer is tailored to installations at home and behind firewalls. If you are installing Pi-hole in an environment beyond that scope, you will need to take extra security measures when installing it.
Pi-hole is very lightweight as it only handles DNS queries and returns a blank HTML file so it doesn’t need much processing power.
- ~52MB of free space
- 512 MB RAM
Pi-hole will run on most Debian-based distro’s and is the preferred platform for it.
We officially support the following:
- Raspbian: Jessie (Only up to Pi-hole v3.2.1) / Stretch (lite / with pixel)
- Ubuntu: 16.04 / 16.10
- Fedora: 26 / 27
- Debian: 8 / 9
- CentOS: 7 (not ARM)
Pi-hole needs a static IP address to properly function (a DHCP reservation is just fine). Users may run into issues because we currently install
dhcpcd5, which may conflict with other running network managers such as
As part of our install process, we append some lines to
/etc/dhcpcd.conf in order to statically assign an IP address, so take note of this prior to installing.
Please be aware of this fact because it may cause confusion. This is not the ideal situation for us to be in, but since a significant portion of our users are running Pi-hole on Raspbian; and because Pi-hole’s roots began with the Raspberry Pi, it’s a problem that is difficult problem to get away from.
Due to the complexity of different ways of setting an IP address across different systems, it’s a slow process and we need help. If you’re willing to contribute, please let us know.
We need ports 53, 80, and 4711. Port 80 is optional if you decide not to install the Web dashboard during installation.
Port 53 should be used by
If you happen to have another DNS server running, such as BIND, you will need to turn it off in order for Pi-hole to respond to DNS queries.
Port 80 should be used by
If you have another Web server already running, such as Apache, Pi-hole’s Web server will not work. You can either disable the other Web server or change the port on which
lighttpd listens, which allows you keep both Web servers running.
Port 4711 should be used by
FTL is our API engine and by default uses port 4711, but will increment if it’s already in use by something else.