Pull request: 3142 custom private subnets

Merge in DNS/adguard-home-wiki from 3142-custom-subnets to master

Squashed commit of the following:

commit b122a69cb1d751456d9d708f288f8d7f5407da9a
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Thu Mar 17 20:30:58 2022 +0300

    Configuration: add versions

commit 9ef9a34f7531bea7727a462cb11e0a13704be64e
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Thu Mar 17 20:09:39 2022 +0300

    Configuration: add private networks
Eugene Burkov 2022-03-18 13:37:43 +03:00
parent 6044426a6d
commit beffaec59c

@ -353,12 +353,16 @@ 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
- `private_networks` (**since v0.108.0-b.5**) — List of networks used to
check if an IP address belongs to a locally-served address registry. If
empty, AdGuard Home will use the set defined by RFC 6303.
- `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
OS.
OS. **Since v0.108.0-b.4** the domain-specific upstreams are validated
for being a valid ARPA domain pointing to a locally-served network.
- `all_servers` — Enables parallel queries to all configured upstream
servers to speed up resolving.