From 7875c0b314a0561c1f230c654e5f4808248ce7ea Mon Sep 17 00:00:00 2001 From: Eugene Burkov Date: Mon, 22 Apr 2024 19:17:40 +0300 Subject: [PATCH] Pull request 197: 6882 Extend private rDNS Squashed commit of the following: commit b314e034dbd51fa0302e9eeea66ee0163b105729 Author: Eugene Burkov Date: Thu Apr 18 16:27:22 2024 +0300 Configuration: imp tagging commit a0ea90c39f035b470666d3b73a0d23cc9bdb515a Author: Eugene Burkov Date: Thu Apr 18 16:22:51 2024 +0300 Configuration: mention soa and ns --- Configuration.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Configuration.md b/Configuration.md index 57b2ad9..1bc30bb 100644 --- a/Configuration.md +++ b/Configuration.md @@ -241,7 +241,7 @@ a workaround, convert them to Punycode (e.g. `xn--e1afmkfd.xn--p1ai` or Using the domain-specific upstream notation, you can specify dedicated upstream DNS servers for reverse DNS (rDNS) requests. If you want **all** your `PTR` -queries to be redirected to `192.168.8.8`: +queries with ARPA domain to be redirected to `192.168.8.8`: 1. Enter the following into the “Upstream DNS servers” field on the “Settings → DNS settings” page: @@ -288,6 +288,9 @@ configuration file. If it is disabled, the unknown addresses from locally served networks won't be resolved at all, and clients performing these queries will receive `NXDOMAIN` responses. +**Since v0.107.49** the `SOA` and `NS` requests are also checked for implying +private rDNS and are resolved according to the same rules as `PTR` before. + #### Public addresses If you want AdGuard Home to use another DNS server for a specific IP address