From e7921e7d26f0670e02d61cd08d71c0825e27654c Mon Sep 17 00:00:00 2001 From: Simon Zolin Date: Mon, 11 Nov 2019 18:21:06 +0300 Subject: [PATCH] + Configuration: add "Specifying upstreams for rDNS" section --- Configuration.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/Configuration.md b/Configuration.md index 9a2d606..6188be1 100644 --- a/Configuration.md +++ b/Configuration.md @@ -5,6 +5,7 @@ Most of these settings can be changed via the web-based admin interface. However * [Command-line arguments](#command-line) * [Configuring upstreams](#upstreams) * [Specifying upstreams for domains](#upstreams-for-domains) + * [Specifying upstreams for rDNS](#upstreams-for-rdns) * [Configuring clients friendly names](#friendly-names) * [Configuration file](#configuration-file) * [Reset Web Password](#password-reset) @@ -81,6 +82,17 @@ If one or more domains are specified, that upstream (`upstreamString`) is used o ``` Sends queries for `*.host.com` to `1.1.1.1:53` except for `*.maps.host.com` which are sent to `8.8.8.8:53` (as long as other queries). + + +### Specifying upstreams for rDNS + +AdGuardHome automatically gets the names of connected devices using rDNS. It sends a PTR request with an IP address of a client to a DNS server and uses its name for "clients friendly names". But what if you want AdGuardHome to use another DNS server for a specific IP address range? You can do it using the same syntax as for general upstream servers, for example: + + [/168.192.in-addr.arpa/]192.168.0.1 + +This rule instructs AdGuardHome to use `192.168.0.1` DNS server for all rDNS requests to resolve clients' IP addresses `192.168.0.0/16`. + + ## Configuring clients friendly names