Expected Behaviour:
Pi-Hole works correctly (as before the network change)
Actual Behaviour:
Pi-Hole does not work with wirelessly connected devices, only with devices connected to the switch.
Debug Token:
5auq5678pl
Comment/Situation Description
Allright, have a bit of an unique situation.
-
I run Pi-Hole through a Ubuntu VM on my linux server. Ubuntu VM has 4 cores, 512 mb of ram and does nothing else than running Pi-Hole, installed with the bash script.
-
I recently had some changes in my network: Before, I had a router/switch/wireless AP combination (D-Link DIR-850L), that gave out IP addresses in the format 10.124.161.***.
-
Now, I have another router, that gives out IP addresses in the format 192.168.0.***, an unmanaged switch (TP-Link TLS-G1008p) and a Ubiquity Unifi AC AP Pro connected to the switch. My server with the Pi-Hole VM is also directly connected to the switch. The Ubiquity Unifi AP gets it IP address & DNS through DHCP.
-
I fill out the DNS manually on the devices I want Pi-Hole on, since I don't want it on all devices (so I'm not using the Pi-Hole DHCP server). On devices that are wired directly into the switch, DNS requests are sent to the pi-hole. On devices that are connected wireless to the Unifi AP (with static dns & ip set on the device), DNS requests are not sent to the Pi-Hole.
-
I checked that every device is configured with the new format static IP's as it should be + did a complete reinstall of the Pi-Hole VM so that it also is correctly configured with the right IP.
Anyone already experienced this? Sorry for the long explanation.
P.S.: Unifi AP does not hand out its own ip addresses, devices connected to unifi ap get ip addresses from router DHCP server