Pi-hole add-on isn’t working

Third party integrations
1

I’m using the Pi-hole add-on, and it was working perfectly until a reboot. After physically restarting Home Assistant, Pi-hole only receives PRT (Port) requests.

In the Home Assistant terminal, I ran some commands. I suspect that the Pi-hole container is no longer running in host network mode. If I reinstall the Pi-hole add-on, everything starts working again. Is there a way to check what network mode the add-on is running in, and change it to host?

→ ~ dig google.com @192.168.0.116
;; communications error to 192.168.0.116#53: connection refused
;; communications error to 192.168.0.116#53: connection refused
;; communications error to 192.168.0.116#53: connection refused;
 <<>> DiG 9.18.34 <>> google.com @192.168.0.116

→ ~ nslookup google. com 192.168.0.116
;; communications error to 192.168.0.116#53: connection refused
;; communications error to 192.168.0.116#53: connection refused
;; communications error to 192.168.0.116#53: connection refused
;; no servers could be reached

Pi-hole dashboard
Pi-hole dashboard1916×1536 196 KB

2

Are you using this integration?
image

I was using a different pi-hole integration and it stopped working a while ago after an HA update. This version works well.

3

No, I’m not using the Pi-hole integration — I’m using a third-party Pi-hole add-on

4

I know the hostname of the Pi-hole add-on — 0da538cf-pihole, and I’m wondering if there’s a command in the Home Assistant terminal that I can use to check the network mode of the add-on — whether it’s using host or bridge, because it seems to me that Pi-hole doesn’t have access to the network.

5

Add-on, so HA OS, so Host mode.

1 Like
6

I was overcomplicating things :slight_smile: Although I had reserved a local IP address on the router, for some reason the IP address of Home Assistant changed after a reboot. I set the new Home Assistant address as the router’s DNS, and everything started working again. Thanks!

1 Like