I'm using Pi-hole (as a secondary DNS server) through TrueNAS SCALE v25 and suddenly had trouble updating Gravity:
My resolv.conf is showing 127.0.0.11 as the only namespace:
I manually updated the config to look like the Pi-hole running on my Raspberry Pi by using echo "" > resolve.conf, and then Gravity worked, but that's a hack method. I wanna figure out why it's wrong and if I can fix it. It used to work, so maybe something changed in the Docker image?
Please don't necro old topics, especially not those that have a solution that apparently didn't apply to your situation.
I've split your posts into a separate topic, allowing it to find a separate solution.
How did you install Pi-hole on TrueNAS?
Note that TrueNAS is not supported by Pi-hole - specifically, the Pi-hole team does not develop nor endorse a TrueNAS Pi-hole app that some users have reported to use.
And please edit your initial post to provide a description of the actual issue you are observing.
I installed Pi-hole using their "Discover apps" method. It's an official TrueNAS UI on top of the standard Docker image.
From what you said, it's not supported via Docker, but I didn't wanna set up another Raspberry Pi for this either.
The reason? If I restart the Raspberry Pi or restart one of my switches (it's connected via PoE), I don't want my whole network going down. My NAS is always on and will take over as the secondary DNS server. I'd make it the primary DNS server, but I'd rather have a dedicated server like a Raspberry Pi for that purpose as my NAS is a multi-purpose server, not just a DNS server.
I'd also like to ensure my settings are synced between both, but right now, I'm doing that stuff manually.
No, I said TrueNAS is not a supported OS.
If that TrueNAS Pi-hole app is just a wrapper around Pi-hole's official Docker image, then it should run, provided the Pi-hole container is configured correctly.
Please share the docker-compose or docker run script you are using to start your Pi-hole container.
