-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Custom reverse lookup fails on OpenWRT #7364
Comments
Possibly related to #4290, however in my case no IPv6 is involved. |
tcpdump seems to confirm that AGH is not querying the configured upstream servers.
And here a tcpdump of me querying AGH with
AGH does not seem to query the upstream server 127.0.0.1:5353. |
Try adding |
Finally had some time to debug. Turns out, the problem seems to be in the documentation. The documentation for reverse lookups says
and
That is not correct. The patterns also need to go into “Private reverse DNS servers”. Then it works as expected. |
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
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, ARM64
Installation
Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)
Setup
On one machine
AdGuard Home version
v0.107.53
Action
I have AGH set up on OpenWRT. Because I have different subnets with different domain names, I have multiple instances of dnsmasq running:
Port 5352 for 192.168.2.0/24
Port 5353 for 192.168.3.0/24
I can successfully resolve IP via those instances e.g. with
nslookup 192.168.3.6 127.0.0.1:5353
In AGH I have the following entries in my upstream servers list:
Additionally, I have the following configuration in the private reverse DNS servers list:
"Use private reverse DNS servers" is checked.
I can successfully resolve *.iot.gofferje.net and *.voice.gofferje.net via AGH but the reverse lookups fail with NXDOMAIN. As mentioned above, I can do the reverse lookup successfully when telling nslookup to contact the respective dnsmasq instance directly, so it appears to be a problem with AGH.
Expected result
Reverse lookup
Actual result
NXDOMAIN
Additional information and/or screenshots
OpenWrt SNAPSHOT (r27777-4d81f40d63)
The text was updated successfully, but these errors were encountered: