Router IP is showing under top client list

[apoh1985]

Hi, just set up adguard home on my raspberry pi. Wondering is it ok for router's IP to show up on top client list?

[Dynamic5912]

How have you set it up in your router?

Is AGH IP set on the WAN/Internet DNS or LAN DNS?

[apoh1985]

i see. alright. let me try that.

just wanted to know what is the best way if i dont use YazFi as i am currently using dns director and setting the guest network profile to my AGH IP. but somehow cant see the client's hostname under "Top Client"

[Dynamic5912]

Guest network behaves different with out of the box settings - hence why YazFi is needed.

It's been a while since I ran a Merlin router but I seem to remember similar issues.

[apoh1985]

alright. let me try YazFi.

anyway i set this into my upstream DNS server field on the AGH in order to see the hostname of clients. 127.0.0.1:5335 is for unbound. is it right to do this?
127.0.0.1:5335
[/168.192.in-addr.arpa/]192.168.50.1

[Dynamic5912]

If unbound is listening on that port then yes.

Are you running unbound on the router or the pi?

[apoh1985]

i am running unbound on pi.

sadly, just went to take a look at YazFi. Seem like it is not supported for the version of the firmware.

[BORGESAG]

It's harmless. It just means your devices are sending their DNS queries to the router, and the router forwards them to AdGuard Home. That's also what Dynamic5912's question is getting at.

If the Pi's IP is only set as the router's WAN/Internet DNS, DHCP still hands out the router itself as the DNS server. Every device asks the router, the router asks AdGuard Home, so AdGuard Home only ever sees the router's IP and all the traffic lands under that one client.

To see each device separately, point the devices at AdGuard Home directly:

1. In the router's DHCP/LAN settings, set the DNS server it hands out to clients to the Pi's IP. The AdGuard Home getting-started guide describes this in the Router section: find the DHCP/DNS settings and enter your AdGuard Home server addresses there.
2. Reconnect the devices, or wait for their DHCP lease to renew, so they pick up the new DNS server.
3. Check on a device with nslookup example.org. The "Server" line should show the Pi's IP, not the router's.

You can keep the Pi as the WAN DNS as well, so the router's own lookups also go through AdGuard Home.

If your router doesn't let you change the DNS server it hands out, the same guide suggests running AdGuard Home as the DHCP server instead. That needs a static IP on the Pi.

• Getting started (Router section): https://adguard-dns.io/kb/adguard-home/getting-started/
• DHCP: https://adguard-dns.io/kb/adguard-home/dhcp/
• Same symptom, same fix: Only client doing requests is my router #7201

[apoh1985]

yes, this is what i have done. i already set the IP under LAN DHCP server but somehow my router are being shown under the "top client" list so i was kind of puzzled. it is suppose to be like that?