cameri on Nostr: The pi-hole was leasing an IP from DHCP on the correct VLAN. VLAN 6 (10.0.4.0/24) -> ...
The pi-hole was leasing an IP from DHCP on the correct VLAN.
VLAN 6 (10.0.4.0/24) -> 10.0.4.5 Assigned & Reserved
Only devices in the same VLAN (and Network) would be logged by Pi-Hole. Devices in other VLANs had 10.0.4.5 as DNS server but would refuse to show up on Pi-Hole logs, however, DNS resolution worked just fine ¿¿¿???.
dig yahoo.com `@10.0.4.5` -> resolved successfully on hosts in other VLANs. But Pi-Hole would not log it. I’m not sure what black magic is that. I have `unbound` running in the pi-hole to serve DNS queries recursively, it’s bound to 127.0.0.1:5335 so it’s not in conflict because it can’t be accessed from remote hosts anyway.
VLAN 6 (10.0.4.0/24) -> 10.0.4.5 Assigned & Reserved
Only devices in the same VLAN (and Network) would be logged by Pi-Hole. Devices in other VLANs had 10.0.4.5 as DNS server but would refuse to show up on Pi-Hole logs, however, DNS resolution worked just fine ¿¿¿???.
dig yahoo.com `@10.0.4.5` -> resolved successfully on hosts in other VLANs. But Pi-Hole would not log it. I’m not sure what black magic is that. I have `unbound` running in the pi-hole to serve DNS queries recursively, it’s bound to 127.0.0.1:5335 so it’s not in conflict because it can’t be accessed from remote hosts anyway.