As is...
Initial state:
- Query ➔ Dnsmasq ➔ Upstream
After enabling AdGuard Home:
No port forwarding
dhcp.@dnsmasq[0].noresolv
➔ '1'
dhcp.@dnsmasq[0].server
➔ '127.0.0.1#3053'
- Query ➔ Dnsmasq ➔ AGH ➔ Upstream
After enabling "AdGuard Home Handle Client Requests":
dport='53'
redirects to dest_port='3053'
dhcp.@dnsmasq[0].noresolv
➔ '1'
dhcp.@dnsmasq[0].server
➔ '127.0.0.1#3053'
- Query ➔ AGH ➔ Upstream
Issue?
-
Dnsmasq resolving is needed to get DHCP clients' addresses.
-
It can be set by manually, but every time restarting AGH or reboot causes change
dhcp.@dnsmasq[0].noresolv
to'1'
anddhcp.@dnsmasq[0].server
to'127.0.0.1#3053'
. -
So currently I can't check where the query was came from.
Hope to be...
Enable "AdGuard Home Handle Client Requests"
dport='53'
redirects to dest_port='3053'
(No change)
dhcp.@dnsmasq[0].noresolv
➔ '0'
(Revert back to initial state)
dhcp.@dnsmasq[0].server
➔ Delete (Revert back to initial state)
Then set AGH upstream to 127.0.0.1:
- Query ➔ AGH ➔ Dnsmasq ➔ Upstream
In addition, I think it would be better to have 127.0.0.1 as default upstream to follow the resolv.conf
. Currently many people will be using slower DNS servers, unless change the upstream settings in AGH.
In my case, 1.1.1.1
takes 4-6 ms regardless of ISP. But the default 9.9.9.9
takes 67-70 ms or 35-40 ms depending on ISP. Of course RTT and throughput are not proportional, but the latter too has pretty decent overseas IX.