Pi-hole version is v5.3.1 (Latest: v5.3.1)
AdminLTE version is v5.5 (Latest: v5.5)
FTL version is v5.8.1 (Latest: v5.8.1)
-
Pihole1
= Ubuntu Server 20.04.2 VM (Hyper-V host - type 2) -
Pihole2
= Raspbian GNU/Linux 10 (buster) Lite (Raspberry Pi 3 Model B Plus Rev 1.3) -
Pihole4
= Ubuntu Server 20.04.2 VM (VMware ESXi host - type 1)
All three appliances have Pi-hole with Unbound, via the official guide -- two of which were built/rebuilt this week. Only Pihole1
functions as desired.
Long story short, my 16GB SanDisk Ultra micro SD card finally gave up its ghost after 3+ years of daily writes (thanks for help resolving that). In the process of rebuilding, I now notice that my traffic on the "IoT" VLAN stopped passing requests to Pihole2
& Pihole4
. I have repaired/reconfigured the failing devices, to no avail. The brand new VM works (Pihole1
), but repeating the same steps on my RPi (and backup VM) do not seem to resolve my issues. Going on day 3 of banging my head against the wall, perhaps someone can help pick out the obvious misconfiguration.
Expected Behaviour:
I expect all the Pi-holes to work across all VLANs with Conditional Forwarding set to 192.168.0.0/16 when listening behavior is set to all (local) interfaces.
Actual Behaviour:
- No DNS across IoT VLAN (192.168.107.0/24)
- running
tcpdump -npi ath1 port 5353
shows all the Multicast traffic, but with (Cache flush??) issues
19:19:24.494075 IP 192.168.107.73.5353 > 224.0.0.251.5353: 0 PTR (QM)? _ewelink._tcp.local. (37)
19:19:24.494248 IP 192.168.107.73.5353 > 224.0.0.251.5353: 0 [2q] [3n] ANY (QM)? Google-Home-Mini-4431075acaf23668f0fc6ce376e9d68a._googlecast._tcp.local. ANY (QM)? 4431075a-caf2-3668-f0fc-6ce376e9d68a.local. (358)
19:19:24.659733 IP 192.168.107.73.5353 > 224.0.0.251.5353: 0 [2q] [3n] ANY (QM)? Google-Home-Mini-4431075acaf23668f0fc6ce376e9d68a._googlecast._tcp.local. ANY (QM)? 4431075a-caf2-3668-f0fc-6ce376e9d68a.local. (358)
19:19:24.929889 IP 192.168.107.73.5353 > 224.0.0.251.5353: 0 [2q] [3n] ANY (QM)? Google-Home-Mini-4431075acaf23668f0fc6ce376e9d68a._googlecast._tcp.local. ANY (QM)? 4431075a-caf2-3668-f0fc-6ce376e9d68a.local. (358)
19:19:26.219722 IP 192.168.107.73.5353 > 224.0.0.251.5353: 0*- [0q] 4/0/0 PTR Google-Home-Mini-4431075acaf23668f0fc6ce376e9d68a._googlecast._tcp.local., (Cache flush) TXT "id=4431075acaf23668f0fc6ce376e9d68a" "cd=95CCC34A92DC7C7CBEF403AA997787C0" "rm=" "ve=05" "md=Google Home Mini" "ic=/setup/icon.png" "fn=Google_Coral" "ca=199172" "st=0" "bs=FA8FCA3F45EF" "nf=1" "rs=", (Cache flush) SRV 4431075a-caf2-3668-f0fc-6ce376e9d68a.local.:8009 0 0, (Cache flush) A 192.168.107.73 (360)
19:19:27.241152 IP 192.168.107.73.5353 > 224.0.0.251.5353: 0*- [0q] 4/0/0 PTR Google-Home-Mini-4431075acaf23668f0fc6ce376e9d68a._googlecast._tcp.local., (Cache flush) TXT "id=4431075acaf23668f0fc6ce376e9d68a" "cd=95CCC34A92DC7C7CBEF403AA997787C0" "rm=" "ve=05" "md=Google Home Mini" "ic=/setup/icon.png" "fn=Google_Coral" "ca=199172" "st=0" "bs=FA8FCA3F45EF" "nf=1" "rs=", (Cache flush) SRV 4431075a-caf2-3668-f0fc-6ce376e9d68a.local.:8009 0 0, (Cache flush) A 192.168.107.73 (360)
- if I bring the test VM up (
Pihole1
) all my devices almost immediately resume responding and I can see the dNAT rules counting up (see above image), so i know my router is properly configured yet i am STILL unable to properly mirror the settings to get everything back up and running. The only thing I'm certain off at this point, is PEBKAC. Thanks, yer nice.
Debug Token:
https://tricorder.pi-hole.net/ocfm3dqq8t
EDIT: If there's anything further I've neglected to provide, please just say the word and I'll follow-up this evening.