Can some explain why you would / wouldn't want to use AdGuard Home Handle Client Request
Toggled off, adguard is still doing my clients DNS but they just appear as localhost, so I'm guessing in theory they are getting forwarded from the router to adguard home but ultimately adguard is "handling the client request" as it's using the upstream of adguard home?
If the toggle is off then does this mean that the router itself is not using the adguard DNS upstream servers, to check for package updates, firmware updates?
To sum up I would also like to know the pros / cons, any added latency for request depending on the option chosen?
I can have it toggled on and policy routing per client works fine, obviously domain routing doesn't as per the tooltip information.
I also know that if you toggle the settings on them each client will show as making it's own request which is great to see what's going on, also by doing so I can then create client rules for certain services so ideally I would want to keep it toggled on but without understanding fully any implications I have just toggled between to test.
Ok so what about "client devices will be handled directly by Adguard home" as opposed to what, how are they handled in the current state when it's toggled off? But adguard home itself is enabled.
From my understanding I believe this option makes all DNS queries use adguard. If I'm using client VPN software on a device I don't want adguard to override.
I'm not interested in knowing which device makes a specific DNS query. Some things are better off not knowing.
You have more control if you can see each individual clients. For example you can create a client profile inside adguard home and then block services on a per client basis (tiktok, YouTube) which is really good for young children, it was one reason I switched from pi hole when they didn't support per client blocking and a feature that wasn't really available in pfblockerng when I was running pfsense - being able to restrict on a per client basis as opposed to everyone has it's perks. Not sure if you knew that was possible
That doesn't sound right. On my android phone I simply used 8.8.8.8 and also I used the quad 9 unencrypted DNS with the same results, they bypass adguard home. If by toggling on that option all DNS should route via Adguard even if the clients are using there own DNS then that's not working as expected.
On my old firewall I simply just created a rule to redirect DNS ports to the router which then forces the clients to use adguard home regardless what the clients DNS is set to.
I am having an issue on my MT6000. I have set 'AdGuard Home Handle Client Requests' on, but it still reports DNS entries as '127.0.0.1' for all queries.
Refer to this post:
This issue is known, it affects the ADG Client list and ADG Query log.
And it already in the develop plan to improve the DNS processes processing flow about the ADG/VPN/Dnsmasq. Thanks.
