Closed mathquis closed 2 years ago
Turns out the previous DNS Rewrite system (v0.106) worked even if the client does not use "Use global settings" (unfiltered DNS resolution).
The new system only works when using this option.
Closing.
Have a look under Filters
» DNS Rewrites
. Maybe that helps.
[ x ] I am running the latest version [ x ] I checked the documentation and found no answer [ x ] I checked to make sure that this issue has not already been filed
Issue Details
Added a custom rule in the textarea :
||mydomain.com^$dnsrewrite=NOERROR;A;<ip>
GUI respond with the correct rule
nslookup mydomain.com <adguard-ip>
on Windows 10 (64 bits) respondNon-existent domain
Version of AdGuard Home server:
How did you install AdGuard Home:
How did you setup DNS configuration:
If it's a router or IoT, please write device model:
CPU architecture:
Operating system and version:
Expected Behavior
nslookup mydomain.com <adguard-ip>
should respond with the IP configured in the rewrite:<ip>
Screenshots