So ASUS routers send a few DNS queries every second to check if an internet connection is active or not... After I changed the WAN DNS from my Pi's IP to 8.8.8.8, 8.8.4.4, I noticed a downward spike in the graphs, but shortly, a spike in queries from localhost:
So I'm assuming that any DNS query the router will be making (like NS resolution for ping/traceroute) will be forwarded to the IPs set in WAN DNS settings?
The Mac has got two DNS servers configured.
This Mac will sometimes also query the not Pi-holed DNS server 10.0.0.1 resulting in the "pi.hole" name not resolving and ads leaking through.
He probably configured his routers DHCP service to push the Pi-hole IP address to his clients for DNS resolution
Can you post screenshots of your router's DHCP settings ?
If settings lacking/missing, you can disable the DHCP service on the router and use Pi-hole's own DHCP service as a replacement:
But the thing is that the router advertises it's own server, and there is no way to disable that unless you turn off DHCP. I do not want to use pi hole as my DHCP server.
If the router doesnt block DHCP and/or DNS for those network segments, it should work.
EDIT: worst case, you can configure a bridge interface on Pi-hole that has a leg/connection to both networks.
EDIT2: below posting describes a bridge setup.
Though I made a mistake and the WiFi SSID and password should be configured in the wpa_supplicant config file.
Not out of the box.
But maybe in some other way.
You have for example the "/etc/hosts" file on Pi-hole where you can configure names to IP.
Pi-hole reads this hosts file on startup.
Because I want to see how many devices are connected, how much bandwidth each is pulling, limit internet speeds on a device, from both the web UI and the ASUS Router app.
EDIT: Never mind, devices are showing up in the router's UI.
I cant think of anything to achieve that but maybe someone else does.
EDIT: our postings crossed again.
Keep in mind if you changed DHCP settings/server, the clients need to renew their DHCP leases to recieve new configured settings etc.
Disconnect & reconnect network or reboot them.