Run PiHole on your UDM

Features

Run PiHole on your UDM with a completely isolated network stack. This will not port conflict or be influenced by any changes on by Ubiquiti
Persists through reboots and firmware updates. After a FW update you will need to resetup your on-boot described in this repo

Requirements

You have setup the on boot script described in this repo (https://github.com/boostchicken/udmpro-utilities/tree/master/on-boot-script)

Steps

On your controller, make a Corporate network with no DHCP server and give it a vlan. The files in this repo assume VLAN 5
Install the CNI plugins with install-cni-plugins.sh
Create podman macvlan network. Copy udm-files/20-dns.conflist to /mnt/data/podman/cni (or a place of your choosing and update on_boot.sh symlink)
Update your on_boot.sh to include the commands in udm-files/on_boot.sh. You can leave out the iptables stuff if you don't want to DNAT all DNS calls to your PiHole
Execute on_boot.sh
Run the pihole docker container, be sure to make the directories for your persistent pihole configuration. They are mounted as volumes in the commmand below.

 podman run -d --network dns \
    --name pihole \
    -e TZ="America/Los Angeles" \
    -v "/mnt/data/etc-pihole/:/etc/pihole/" \
    -v "/mnt/data/pihole/etc-dnsmasq.d/:/etc/dnsmasq.d/" \
    --dns=127.0.0.1 --dns=1.1.1.1 \
    --hostname pi.hole \
    -e VIRTUAL_HOST="pi.hole" \
    -e PROXY_LOCATION="pi.hole" \
    -e ServerIP="10.0.5.3" \
    pihole/pihole:latest

Set pihole password

podman exec -it pihole pihole -a -p YOURNEWPASSHERE

Update your DNS Servers to 10.0.5.3 in all your DHCP configs.
Access the pihole like you would normally. http://10.0.5.3/

1.7 KiB Raw Blame History

Run PiHole on your UDM

Features

Requirements

Steps

1.7 KiB

Raw Blame History