mirrors/AdGuardHome
1
0
Fork 0
mirror of https://github.com/AdguardTeam/AdGuardHome.git synced 2025-03-15 06:59:00 +03:00
Code Issues Projects Releases Packages Wiki Activity

Pull request: 3184 disable private ptr 

Merge in DNS/adguard-home-wiki from 3184-private-ptr to master

Squashed commit of the following:

commit 405f9970c75d0e2e1c2ede4c0a42b8f694327a6c
Author: Eugene Burkov <e.burkov@adguard.com>
Date:   Wed May 26 15:41:13 2021 +0300

    Configuration: doc rdns
Eugene Burkov 2021-05-26 18:01:29 +03:00
parent 9558a89a0c
commit 1f41358bb8
1 changed files with 7 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
Configuration.md

@ -117,7 +117,11 @@ The problem with these lists is that they may be too large. In this case you may
AdGuardHome automatically gets the names of connected devices using Reverse DNS lookup (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".
Since **v0.106.0** you can enable and disable this feature by "Enable clients' hostname resolution" setting in the "Upstream DNS servers" section or via `resolve_clients` field in the configuration file. Also since **v0.106.0** all the addresses from [private IP range](https://tools.ietf.org/html/rfc6303) are only resolved via appropriate local resolvers to avoid the leaks of clients' information. But you can also set custom upstreams for it by "Private DNS servers" field in the "Upstream DNS servers" section or by `local_ptr_upstreams` field in the configuration file. Note that the specified upstreams are also used by DNS server to resolve PTR for the same IP range.
Since **v0.106.0** you can enable and disable this feature by "Enable clients' hostname resolution" setting in the "Upstream DNS servers" section or via `resolve_clients` field in the configuration file.
Also since **v0.106.0** all the addresses from [private IP range](https://tools.ietf.org/html/rfc6303) are only resolved via appropriate local resolvers to avoid the leaks of clients' information. But you can also set custom upstreams for it by "Private DNS servers" field in the "Upstream DNS servers" section or by `local_ptr_upstreams` field in the configuration file. Note that the specified upstreams are also used by DNS server to resolve PTR for the same IP range.
Since **v0.107.0** you can control using private reverse DNS upstream servers by "Use private rDNS resolvers" checkbox in the "Upstream DNS servers" section or by `use_private_ptr_resolvers` field in the configuration file. In case it is disabled, the unknown addresses from locally-served networks won't be resolved at all.
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:
@ -210,6 +214,8 @@ Settings are stored in [YAML format](https://en.wikipedia.org/wiki/YAML), possib
- `upstream_dns` — List of upstream DNS servers.
- `upstream_dns_file` — Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
- `bootstrap_dns` — List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
- `use_private_ptr_resolvers` (**since v0.107.0**) – If AdGuard Home should
use private reverse DNS servers.
- `local_ptr_upstreams` (**since v0.106.0**) – List of upstream DNS servers
to resolve PTR requests for addresses inside locally-served networks. If
empty, AdGuard Home will automatically try to get local resolvers from the