Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DnsRewrite rule not working at all #4126

Closed
mathquis opened this issue Jan 11, 2022 · 2 comments
Closed

DnsRewrite rule not working at all #4126

mathquis opened this issue Jan 11, 2022 · 2 comments

Comments

@mathquis
Copy link

[ 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) respond Non-existent domain
  • Version of AdGuard Home server:
    • v0.107.2 and v0.108.0-a.24+e9c59b09
  • How did you install AdGuard Home:
    • Docker
  • How did you setup DNS configuration:
    • Router
  • If it's a router or IoT, please write device model:
    • Freebox
  • CPU architecture:
    • ARM64
  • Operating system and version:
    • Raspbian

Expected Behavior

    • nslookup mydomain.com <adguard-ip> should respond with the IP configured in the rewrite: <ip>

Screenshots

AdGuard-Home
AdGuard-Home (1)

@mathquis
Copy link
Author

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.

AdGuard-Home (3)

Closing.

@ppfeufer
Copy link

Have a look under Filters » DNS Rewrites. Maybe that helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants