client -> router (DNS) -> Pihole (DNS) than it is not possible, because for pihole it looks like all DNS queries coming from your router. You should still see all clients in "Network overview" (if on the same subnet) but with the notion that they are not using pihole (because DNS requests are not send directly to pihole).
Yyou could keep your router as DHCP Server but distribute Pihole's IP as DNS server for the clients.
Sorry to necro and old thread here, but as a new Pi-hole user, I thought I'd ask: Is the best practice here to make Pi-hole the DHCP Server, and not the Router, in order to preserve individual client queries in reporting? Wouldn't that add further overhead to Pi-hole / the Pi ?
I'm using my router as DHCP server and just using Pi-hole as my DNS Server, as recommended in the standard install instructions, but like the OP, I'm only seeing my router as the primary client behind all queries (192.168.1.1).
The Pi-hole DHCP server is an option to show individual clients when the router will not. There is no "best practice" - use what best meets your needs.
Yes, but by a trivial amount. DHCP transactions are done once per lease cycle, which generally is very infrequent.