Comment

You are lucky I haven’t deleted my pi-hole VM yet ;D

In the Pi-Hole DNS settings I have the following configuration:

Upstream DNS Servers => Quad9 (filtered, DNSSEC) both checkboxes for IPv4 checked
Under Custom DNS servers I added a line with my routers IP
Under Interface settings => Permit all origins. Note the warning written regarding this setting and check whether it applies for your setup!
Under Advanced DNS settings I have enabled “Never forward non-FQDN A and AAAA queries” and “Never forward reverse lookups for private IP ranges”. Since according to the warning this would block local hostname resolution note the next setting.
Under conditional forwarding I have added this line true,192.168.1.0/24,192.168.1.1,fritz.box. fritz.box was my local DHCP domain name but has since been changed to lan.

The other settings in Pi-Hole were under the Local DNS Records menu where I added my domain name (let’s call it example.com) to the list of local DNS records and pointed it at the IP of the server running my reverse-proxy. Finally I added each subdomain I wanted to use to the List of local CNAME records and pointed it at the domain I just entered to the other list.

I can’t perfectly tell you what my router settings were unfortunately since I have recently moved and replaced my fritzbox with a mikrotik router. The main thing you have to do though is to go to the DHCP server settings of your router and set the pi-holes IP address as the DNS server. Note that in the case of the pi-hole being offline for any reason you will be unable to resolve any domains while in this network

It might be possible to do some sort of failover setup by running a second pi-hole with identical settings but I did not want my network connectivity depending on any device other than my router being on. Hence my move back to using my mikrotiks built-in DNS server which fortunately also supports adding lists for DNS adblocking.

source

Sort:hotnew top

DevotedOtter@lemm.ee ⁨2⁩ ⁨weeks⁩ ago
Awesome, thanks for the reply. I can understand not wanting to be stuck without DNS if your pihole goes down.

I’m hoping to use just pihole for internal only resolution, so some sort of split DNS, but it may be outside of my capabilities at the moment

source
- Scrath@lemmy.dbzer0.com ⁨2⁩ ⁨weeks⁩ ago
  I’m not sure that’s possible on most routers but I’m very much not an expert in networking
  
  source
  - DevotedOtter@lemm.ee ⁨2⁩ ⁨weeks⁩ ago
    I’m on OPNSense, although relatively new to it. As far as I’m aware, it’s possible, but I’ll dig a bit deeper.
    
    Cheers
    
    source
Eldaroth@lemmy.world ⁨2⁩ ⁨weeks⁩ ago
If your router allows it you can set your gateway IP from the router (i.e. 192.168.1.1) as the second DNS address in the DHCP settings. So your routers DNS settings would then act as fail over in case your pi-hole is down. That’s at least how I have done it on my ISP router.

source
- Scrath@lemmy.dbzer0.com ⁨2⁩ ⁨weeks⁩ ago
  I don’t think that’s how it works with my router. I read a bit about DNS failover and the consensus seemed to be that all DNS servers listed should return equal results since requests are spread round-robin between them (at least for mikrotik routers).
  
  source