mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
DNS rewrite rules to the local ip via router are not working #1879
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#1879
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sandzhaj on GitHub (Aug 13, 2020).
Prerequisites
Issue Details
My setup
The problem is
DNS rewrite rules to the local ip via router are not working
check -> 172.217.16.46.Now if I make request through the router, i get a strange message.
** server can't find check: REFUSEDBut, I don't care. I get the response IP and site opens
check -> 192.168.1.104And I couldn't make it work through the router. I'll get the same error, but without a response
But i can see that request in querry log
Through the router:
Directly to the adguard server Look, we have to records in log for 1 request (via the router we have only one):
What will be great
I want to use default network configuration on my devices (which use router for the dns queries)
And i want to access my local resources with a name.
I don't want to configure all my devices to the adguard server, because in that case it is the similar as making some lines in /etc/hosts
I understand that it could be an issue from the router side, but at the same time - any other responses are working, so maybe it is a problem with an adguard responses
@szolin commented on GitHub (Aug 14, 2020):
It seems like your router doesn't send AAAA request for
checkhost name, but replies to you with REFUSED instead. This may be a router's configuration issue. You have to find our what causes your router to behave this way. AGH works fine and replies to AAAA request as it should - your screenshot proves that.I only can suggest to try e.g.
check.localorcheck.cominstead ofcheck.@sandzhaj commented on GitHub (Aug 14, 2020):
But why router sends AAAA with any other domains that are not in rewrite rules? Like for google?
If in one case router sends, and in another case it doesn't, I supposed to think, that in that cases AGH responses differ
I tried with mydomain.org, subdomain.mydomain.org
Even with google.com, if I create a rewrite (google.com -> 192.168.1.106), I'll get the strange behavior
Direct:
Via router:
@stale[bot] commented on GitHub (Oct 13, 2020):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.