Using Pi-hole with Unbound: Difference between revisions

From Alpine Linux
m (added unbound)
(moved headings with some clarifications)
Line 3: Line 3:
== Prerequisites ==
== Prerequisites ==


* You should have a {{Pkg|dnsmasq}} (or another DHCP server/router) on your network as DHCP functions of Pi-hole is not used here.
* A {{Pkg|dnsmasq}} (or another DHCP server/router) on the network, as DHCP function of Pi-hole is not used here.


== Installation ==
== Installation ==
Line 19: Line 19:
=== Unbound configuration ===  
=== Unbound configuration ===  


Create a file {{Path|/etc/unbound/unbound.conf.d/pi-hole.conf}} based on the content given in [https://docs.pi-hole.net/guides/dns/unbound unbound page of Pi-hole website].
Create a file {{Path|/etc/unbound/unbound.conf.d/pi-hole.conf}} based on the content given in [https://docs.pi-hole.net/guides/dns/unbound/#configure-unbound unbound page of Pi-hole website].


[[Setting_up_unbound_DNS_server#Download root hints|Download root hints]] for the Unbound server.
[[Setting_up_unbound_DNS_server#Download root hints|Download root hints]] for the Unbound server.
Line 27: Line 27:


Once the above changes are made, [[Setting_up_unbound_DNS_server#Service_management|check the unbound config and restart the unbound service]].
Once the above changes are made, [[Setting_up_unbound_DNS_server#Service_management|check the unbound config and restart the unbound service]].
== Service management ==
Add the {{ic|pihole}} service to auto-start using [[OpenRC]]: {{Cmd|$ doas rc-update add pihole default}}
{{ic|pihole}} service can be managed using standard '''start|stop|restart''' [[OpenRC]] commands. To start the service immediately:{{Cmd|$ doas rc-service pihole start}}


== Using web interface ==
== Using web interface ==


Start the {{ic|pihole}} service as per command given in [[#Service management|Service management]] section. Once the {{ic|pihole}} service is started, connect to pihole web interface for further steps: '''https://192.168.1.3/admin/'''  
The Pi-hole web interface can be used only if the {{ic|pihole}} service is started as per instructions in the [[#Service management|service management]] section. Once the {{ic|pihole}} service is started, connect to Pi-hole web interface for further configuration: '''https://192.168.1.3/admin/'''  


=== Enable recursive DNS ===
=== Enable recursive DNS ===
Line 47: Line 53:


Enjoy Ad-Free browsing!
Enjoy Ad-Free browsing!
== Service management ==
Add the {{ic|pihole}} service to auto-start using [[OpenRC]]: {{Cmd|$ doas rc-update add pihole default}}
{{ic|pihole}} service can be managed using standard '''start|stop|restart''' [[OpenRC]] commands. To start the service immediately:{{Cmd|$ doas rc-service pihole start}}


== See also ==
== See also ==
 
* [https://docs.pi-hole.net/ Official Pi-hole documentation]
* [https://docs.pi-hole.net/guides/dns/unbound/ Pi-hole as All-Around DNS Solution]
* [[Setting_up_unbound_DNS_server|unbound]]
* [[Setting_up_unbound_DNS_server|unbound]]
* [[Using Unbound as an Ad-blocker]]
* [[Using Unbound as an Ad-blocker]]
* [https://docs.pi-hole.net/ Official Pi-hole documentation]
* [https://docs.pi-hole.net/guides/dns/unbound/ Pi-hole as All-Around DNS Solution]


[[Category:Networking]]
[[Category:Networking]]

Revision as of 14:21, 5 November 2025

This page documents the steps to use Pi-hole with unbound as an All-Around DNS Solution along with ad-blocker functionality by using a publicly available blacklist.

Prerequisites

  • A dnsmasq (or another DHCP server/router) on the network, as DHCP function of Pi-hole is not used here.

Installation

Currently the pihole is available in the testing repository. It can be safely installed by following the guidelines for enabling the testing repo and for installing such packages with the use of the @testing tag.

The command below installs necessary packages:

$ doas apk add pihole@testing unbound

Configuration

Add your local user to the 'pihole' group as follows:

$ doas addgroup $USER pihole

Note: This section uses 192.168.1.3 as IP address of Pi-hole server, while the Internet gateway router/DHCP server is at 192.168.1.1

Unbound configuration

Create a file /etc/unbound/unbound.conf.d/pi-hole.conf based on the content given in unbound page of Pi-hole website.

Download root hints for the Unbound server.

Ensure that the /etc/unbound/unbound.conf file has only the following line uncommented:

Contents of /etc/unbound/unbound.conf

# All lines are to be commented out like this, except the below ... include-toplevel: "/etc/unbound/unbound.conf.d/*.conf"

Once the above changes are made, check the unbound config and restart the unbound service.

Service management

Add the pihole service to auto-start using OpenRC:

$ doas rc-update add pihole default

pihole service can be managed using standard start|stop|restart OpenRC commands. To start the service immediately:

$ doas rc-service pihole start

Using web interface

The Pi-hole web interface can be used only if the pihole service is started as per instructions in the service management section. Once the pihole service is started, connect to Pi-hole web interface for further configuration: https://192.168.1.3/admin/

Enable recursive DNS

Add unbound to the Custom DNS servers section on the admin page: https://192.168.1.3/admin/settings/dns as follows:127.0.0.1#5335

Remember to Save&Apply to make the changes to Pi-hole permanent.

Add blocklist file

On the Subscribed lists group management page at https://192.168.1.3/admin/groups/lists, add stevenblack list by adding an entry http://sbc.io/hosts/hosts and Click Add blocklist button.

To load the blocklist, Update Gravity (list of blocked domains) by clicking Update on the page https://192.168.1.3/admin/gravity or running the command:

$ pihole -g

Ensure that your clients point their DNS to Pi-hole ip address:192.168.1.3

Enjoy Ad-Free browsing!

See also