Between christmas and new years I have exchanged the old pc for a new one, leaving the linux installation intact (Buster). Doing this broke a lot of things, primarily because the internet adapter changed from enp2s0 to eno1. I spend quite some time getting the server to work... I then also broke the VPN tunnel through pihole and today finally got to fixing this. I also just realized pihole is also no longer blocking ads through my main pc (secondary set to 8.8.8.8) and after forcing it to use the IP of the pi-hole system I cannot seem to resolve the DNS.
The interesting part is that tunneling with openvpn does work, but accessing on a local network seems to fail.
I'm not confident this is a fault on pihole's part, but currently only pihole seems to not work (plus I spend like 3 hours already yawn).
Can you perhaps give me some pointers what I need to kick to get pihole to work on lan again?
Debug Token:
jxz8dbqnct
I should note that I changed the port from 80 to 81, diyHue doesn't want to move.
First, run below one and select Reconfigure to run through all the settings after your changes:
pihole -r
Second, check network interfaces available:
ip l
ip a
And check interface configured for Pi-hole:
grep PIHOLE_INTERFACE /etc/pihole/setupVars.conf
And how Pi-hole is configured to listen to these interfaces:
grep DNSMASQ_LISTENING /etc/pihole/setupVars.conf
If configured to lets say only listen on the eth0 or wlan0 interface, querying Pi-hole's DNS on the other interfaces, like for example the VPN's tun0 IP, will fail.
To have Pi-hole answer DNS queries on all interfaces, change below Pi-hole setting on the web GUI: