mirrors/AdGuardHome
1
0
Fork 0
mirror of https://github.com/AdguardTeam/AdGuardHome.git synced 2024-11-23 13:35:38 +03:00
Code Issues Projects Releases Packages Wiki Activity

Pull request 197: 6882 Extend private rDNS 

Squashed commit of the following:

commit b314e034dbd51fa0302e9eeea66ee0163b105729
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Thu Apr 18 16:27:22 2024 +0300

    Configuration: imp tagging

commit a0ea90c39f035b470666d3b73a0d23cc9bdb515a
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Thu Apr 18 16:22:51 2024 +0300

    Configuration: mention soa and ns
Eugene Burkov 2024-04-22 19:17:40 +03:00
parent e9213804c5
commit 7875c0b314
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
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.
#### <a href="#rdns-public" id="rdns-public" name="rdns-public">Public addresses</a>
If you want AdGuard Home to use another DNS server for a specific IP address