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

Adguard DNS Rewrites not working as they should. Rewrites being processed by public DNS and not local DNS. #7602

Open
SluberskiHomeLab opened this issue Jan 28, 2025 · 0 comments

Comments

@SluberskiHomeLab
Copy link

Discussed in #7601

Originally posted by SluberskiHomeLab January 28, 2025
I have 2 Adguard Home DNS servers setup in LXC containers. About 4-5 months ago, I added DNS rewrites and it was working, but after about a month they have not been resolving locally. I noticed that instead of rewriting to my reverse proxy, the request gets resolved by one of my upstream DNS servers. I've also tried adding my secondary Adguard IP to my upstream with no luck. I've been toying around with this for the past 3-4 months and I'm lost. My rewrite entry is *.slubhome and forwards to my reverse proxy ip address

Here's the result from one of my attempts at accessing my local Adguard sync server (which is in my reverse proxy).

adguard-sync.slubhome

Status - Processed

DNS server - 9.9.9.9:53

Served from cache - [check]

Elapsed - 0.01 ms

Response code - NXDOMAIN

These are my upstream DNS servers:

https://dns10.quad9.net/dns-query

9.9.9.9

1.1.1.1

1.0.0.1

8.8.8.8

I have "Use Private DNS Resolvers" unchecked and "Enable Reverse Resolving of Client's IP Addresses" checked. (I have tried turning both off or both on with no luck.)

Any ideas?

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

1 participant