TrueNAS Pihole router setup

Apps and Virtualization
, ,
1

Hi,

I’m struggling to set up correctly TrueNAS SCALE, Pihole DNS and my old TP-Link router.

It seemingly works, but I can’t update Pihole app via TrueNAS, because after Pihole is down during update, it can’t get back up.

My TrueNAS machine is 192.168.1.11 and on my router I have:

image
image519×505 15.1 KB

This obviously doesn’t work. I’ve searched quite a bit, but can’t really find anything useful on the matter. Any pointers how to configure?

2

Is the issue that you can’t update your DNS while you’re reliant on the DNS that you’re updating?

Could you set TrueNAS to use a public DNS at least temporarily while updating your local DNS?

1 Like
3

While not directly related to your application woes…

  • The NAS should rather have a static IP outside of the DHCP range.
  • Have a public DNS as fallback (your ISP, Quad9, Cloudflare, Google, whatever).
4

I already had a reserved IP, but now I changed DHCP IPs to start at 192.168.1.15 (TrueNAS is still …11)

Still same result:

image
image508×162 2.39 KB

5

But that doesn’t seem like a proper solution. I’d need to do this every time I update the app, wouldn’t I?

6

Ok you could I guess add the update location to hosts. You could add a secondary local DNS.

When DNS is shut down, you need some way to resolve the address for the updates.

7

Assuming it’s not caused by an upstream DNS used in PiHole or the settings in your install, then suggest the work around I’ve used for some time. Set the router DNS to all public and set each client PC’s DNS in Win11 or Linux to the PiHole/Truenas ip address. This setup satisfied my ISP’s proprietary router and allowed updates to the truenas PiHole app.

1 Like