Open mangkoran opened 4 months ago
You're indeed right. I can reproduce.
@ainar-g as explained by @mangkoran the empty domain specification also redirects to the specified upstream the root zone, which is obviusly not expected as it should be sending only unqualified names as per the wiki.
Thank you for your reply. I'm a bit curious and tried to add [/./]8.8.8.8
to "Upstream DNS servers" to see if I can override the upstream for .
. However, I got the following error.
Prerequisites
[X] I have checked the Wiki and Discussions and found no answer
[X] I have searched other issues and found no duplicates
[X] I want to report a bug and not ask a question or ask for help
[X] 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)
OpenWrt, ARM64
Installation
Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)
Setup
On a router, DHCP is handled by the router
AdGuard Home version
0.107.48
Action
Replace the following command with the one you're calling or a description of the failing action:
Expected result
Query forwarded to correct upstream server
Actual result
Root domain (only dot/".") query is forwarded to incorrect upstream which is likely the private reverse DNS server (
127.0.0.1:54
)Additional information and/or screenshots
AGH config:
To test my assumption, I tried to change the
[//]
upstream to8.8.8.8
(there is no8.8.8.8
in my config so this should be a good indicator) and triednslookup
. As we can see the upstream now changes to8.8.8.8
.Am I missing something here? Is the
.
query supposed to be included in[//]
? Because I thought it's not. In the documentation it is said: