AdGuardHome
AdGuardHome copied to clipboard
AdguardTeam
clash fake ip mode ，adguardhome dns test fail
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 report a bug and not ask a question or ask for help
-
[X] I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Linux, AMD64 (aka x86_64)
Installation
Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)
Setup
On a router, DHCP is handled by the router
AdGuard Home version
v0.107.41
Action
i set clash dns server port of adguardhome upstram dns server,but clash is work as fake ip mode.so when i touch test dns buttom it will notice me clash dns server test fail.because its return a fake ip. but it actully work will .
REQUIRE IAMGE
Expected result
TEST SUCCESS
Actual result
TEST FAIL IMAGE
Additional information and/or screenshots
No response
did you use dns utils test this address? e.g: dig www.bing.com @127.0.0.1 -p7874
@wangqaq, which actual part of the returned HTTP response corresponds to this upstream? It may be related to the test we perform for healthchecking the servers, so this one may respond in an unexpected way.
@wangqaq, which actual part of the returned HTTP response corresponds to this upstream? It may be related to the test we perform for healthchecking the servers, so this one may respond in an unexpected way. TEST FAIL IMAGE 127.0.0.1:7874，this is clash dns server,maybe adguardhome test upstream dns server is compare upstream dns server response ip to some domain real ip? because clash work in fake ip mode,it will give a ip such as 192.18.0.15 mapping to that domain to proxy?
@wangqaq, which actual part of the returned HTTP response corresponds to this upstream? It may be related to the test we perform for healthchecking the servers, so this one may respond in an unexpected way. TEST FAIL IMAGE 127.0.0.1:7874，this is clash dns server,maybe adguardhome test upstream dns server is compare upstream dns server response ip to some domain real ip? because clash work in fake ip mode,it will give a ip such as 192.18.0.15 mapping to that domain to proxy?
yes ,clash work in fake-ip mode will give a such as 192.18.0.15 mapping to that domian to proxy,and its not true ip which is domain registered
@wangqaq, which actual part of the returned HTTP response corresponds to this upstream? It may be related to the test we perform for healthchecking the servers, so this one may respond in an unexpected way. TEST FAIL IMAGE 127.0.0.1:7874，this is clash dns server,maybe adguardhome test upstream dns server is compare upstream dns server response ip to some domain real ip? because clash work in fake ip mode,it will give a ip such as 192.18.0.15 mapping to that domain to proxy?
yes ,clash work in fake-ip mode will give a such as 192.18.0.15 mapping to that domian to proxy,and its not true ip which is domain registered
when clash monitor that ip requrst will proxy to ur proxy group node,& i ping that fake ip in cmd, it actually responsed.