Client field in log shows my router address. It should show the actual client.
Prerequisites
-
[x] I have checked the Wiki and Discussions and found no answer
-
[x] I have searched other issues and found no duplicates
-
[x] I want to request a feature or enhancement and not ask a question
The problem
I have a Linksys Mesh system with one node connected to my ISP router (which is in bridge mode). The main Linksys node routes DNS requests to Adguard Home. When I was using Pi-hole, the query logs would show the originator of DNS requests (int the query log) from the actual device that made the request. In Adguard Home, the "client" field is always the Linksys node.
Proposed solution
It must be possible to get the address of the actual originating client (given that pi-hole does it). I propose that Adguard Home does this too.
Alternatives considered and additional information
No response
It does when setup correctly.
How are you pointing your DNS from your router to AGH?
Are you entering it as the WAN DNS or LAN DNS?
I’m having the same issue on a netgear R6700AX that has DNS pointed to AGH.
I’m having the same issue on a netgear R6700AX that has DNS pointed to AGH.
As per above...
If your clients are querying the router, and the router is then querying AdguardHome, the only queries AdGuardHome sees are from the router. If your clients are speaking directly to AdGuardHome, then you'll see the client in AdGuardHome (as well as removing one extra DNS query in every lookup)
This is misconfiguration/misunderstanding, not an AdGuardHome issue.
Aside from EDNS I don't belive there's any way that this could have worked with your PiHole - I expect your clients were directly querying the PiHole.