- Specifying upstreams for domains: simplify ambiguous syntax description

Squashed commit of the following:

commit c78d163bd2ed973df22cda03c7c5168c7fb74ebf
Author: Simon Zolin <s.zolin@adguard.com>
Date:   Thu Apr 23 14:14:54 2020 +0300

    - Specifying upstreams for domains: simplify ambiguous syntax description
Simon Zolin 2020-04-23 15:22:24 +03:00
parent 32c9617e87
commit 1dd187334b

@ -65,7 +65,9 @@ Examples:
You can specify upstreams that will be used for a specific domain(s). We use the dnsmasq-like syntax (see `--server` description [here](http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html)). This feature is intended for private nameservers which deal with intranet domains. You can specify upstreams that will be used for a specific domain(s). We use the dnsmasq-like syntax (see `--server` description [here](http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html)). This feature is intended for private nameservers which deal with intranet domains.
**Syntax:** `[/[domain1][/../domainN]/]upstreamString` **Syntax:**
[/domain1/domain2/domainN/]upstreamString
If one or more domains are specified, that upstream (`upstreamString`) is used only for those domains. Usually, it is used for private nameservers. For instance, if you have a nameserver on your network which deals with `xxx.internal.local` at `192.168.0.1` then you can specify `[/internal.local/]192.168.0.1`, and AdGuard Home will send all queries to that nameserver. Everything else will be sent to the default upstreams (which are mandatory!). If one or more domains are specified, that upstream (`upstreamString`) is used only for those domains. Usually, it is used for private nameservers. For instance, if you have a nameserver on your network which deals with `xxx.internal.local` at `192.168.0.1` then you can specify `[/internal.local/]192.168.0.1`, and AdGuard Home will send all queries to that nameserver. Everything else will be sent to the default upstreams (which are mandatory!).