You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just installed pihole on my UDM-Pro running UniFi OS UDM Pro 1.11.4. It works great, with the exception that pihole doesn't automatically load after a reboot. Any guidance on what to look at to find root cause and how to fix this?
After reboot, I've validated it's not running by executing podman ps and validating that the only image running is localhost/unifi-os:latest
To restart pihole, I have to re-copy 20-dns.conflist to the UDM-Pro, as neither 20-dns.conflist nor dns.conflist exist anymore.
After that, I execute /mnt/data/on_boot.d/05-install-cni-plugins.sh, /mnt/data/on_boot.d/10-dns.sh, and then execute the podman run-d command including options. (It's possible that I could have just executed podman run -d, but didn't test that.)
Because I'm running pihole on my UDM-Pro, I'm only including the pihole IP addr in the DNS server list for DHCP clients. Any reasons why I should add an external DNS besides the pihole IP addr for my DHCP clients?
Assuming I can get pihole to restart after a reboot, I think this is relatively low risk because pihole is pretty stable. I understand the reasons why you'd want to do that if you had pihole running on another network device which introduces a number of potential failure scenarios, but in this case I'm less worried about it because if the UDM-Pro goes down so does my Internet connection. Am I crazy for doing this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I just installed pihole on my UDM-Pro running UniFi OS UDM Pro 1.11.4. It works great, with the exception that pihole doesn't automatically load after a reboot. Any guidance on what to look at to find root cause and how to fix this?
After reboot, I've validated it's not running by executing
podman ps
and validating that the only image running islocalhost/unifi-os:latest
To restart pihole, I have to re-copy 20-dns.conflist to the UDM-Pro, as neither 20-dns.conflist nor dns.conflist exist anymore.
After that, I execute
/mnt/data/on_boot.d/05-install-cni-plugins.sh
,/mnt/data/on_boot.d/10-dns.sh
, and then execute thepodman run-d
command including options. (It's possible that I could have just executedpodman run -d
, but didn't test that.)Because I'm running pihole on my UDM-Pro, I'm only including the pihole IP addr in the DNS server list for DHCP clients. Any reasons why I should add an external DNS besides the pihole IP addr for my DHCP clients?
Assuming I can get pihole to restart after a reboot, I think this is relatively low risk because pihole is pretty stable. I understand the reasons why you'd want to do that if you had pihole running on another network device which introduces a number of potential failure scenarios, but in this case I'm less worried about it because if the UDM-Pro goes down so does my Internet connection. Am I crazy for doing this?
Beta Was this translation helpful? Give feedback.
All reactions