The issue I am facing:
I have VLANs in/on my network.
The only VLAN that uses PiHole's DHCP is the main one.
My question
If it is in PiHole's world of control and I would like to use PiHole as the DHCP server on the OTHER VLANs too.
That way any report I see will have the machine's name rather than its IP address.
I don't know if that is something I should be asking here or elsewhere.
But if I don't ask: I'll never get to know.
Thanks.
Client IPs will show up if they talk to Pi-hole directly, regardless of how they learned to use your Pi-hole for DNS.
If your VLAN clients already are aware of your Pi-hole host machine's IP, but do not show up individually, then your router would be NATting its inter-VLAN traffic, i.e. it would replace the requestor's IP with its own before forwarding it.
That behaviour of your router won't change if you'd shift DHCP duties.
To associate your local, private range client IP addresses with names, Pi-hole has to source those names from somewhere, e.g. by querying your router's DNS server (as sole upstream or via Conditional Forwarding) or by defining Local DNS records.
What this?
No.
Ok, I am wrong - again. (and as usual)
Thoughts on what is going on with those 2 pics?
(Sorry)
I'm not sure I can set a machine name on that software.
Maybe that's the cause?
Could be.
If the client does not present a hostname during DHCP negotiation, and your router does not allow you to assign one, you could create Local DNS records for it.
Ok, thanks.
Seems I am way way WAY outside my understanding.
The first picture (of the two above) shows the DHCP page and the IP address is assigned a name there.
So if it is still happening, I won't bother you. It is outside my skill set.
Thanks.
