You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a router that provides DHCP addresses and local DNS names.
Each DNS record has a PTR address, so I've set the AdGuard "arpa" domain upstream server and the "Private reverse DNS servers" to the router.
Upstream DNS servers
# Local DNS server
[/in-addr.arpa/]192.168.8.1 fd01:192:168:8::1
[/ip6.arpa/]192.168.8.1 fd01:192:168:8::1
[//]192.168.8.1 fd01:192:168:8::1
Private reverse DNS servers
192.168.8.1
fd01:192:168:8::1
Whenever I try to query AdGuard for a PTR record, it fails to find the answer and responds with "NXDOMAIN".
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a router that provides DHCP addresses and local DNS names.
Each DNS record has a PTR address, so I've set the AdGuard "arpa" domain upstream server and the "Private reverse DNS servers" to the router.
Upstream DNS servers
Private reverse DNS servers
Whenever I try to query AdGuard for a PTR record, it fails to find the answer and responds with "NXDOMAIN".
When I track queries in AdGuard interface, I can see that it receives the request and sends it to an external DNS server, not to the router.
So, I'm not sure why AdGuard is not sending requests to the router.
Any thoughts on this matter?
Beta Was this translation helpful? Give feedback.
All reactions