Pull request 185: 4977-multiple-domain-specific-upstreams

Squashed commit of the following:

commit dbfcf02ec1d547413831fd9f0d4fe7543ca6f2fe
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date:   Wed Oct 25 20:35:40 2023 +0300

    Configuration: multiple domain specific upstreams
Stanislav Chzhen 2023-10-27 20:19:15 +03:00
parent 484a397911
commit beebafd906
1 changed files with 13 additions and 0 deletions

@ -117,6 +117,9 @@ The syntax is:
[/domain1/domain2/domainN/]upstreamString [/domain1/domain2/domainN/]upstreamString
``` ```
Where `upstreamString` is one or many upstreams separated by space (e.g.
`1.1.1.1 2.2.2.2`).
If one or more domains are specified, that upstream (here `upstreamString`) is If one or more domains are specified, that upstream (here `upstreamString`) is
used only for those domains. Usually, it is used for private nameservers. For 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 instance, if you have a nameserver on your network which deals with
@ -202,6 +205,16 @@ upstreams.
sends queries for `*.host.com` to `2.2.2.2:53` except for `host.com` queries sends queries for `*.host.com` to `2.2.2.2:53` except for `host.com` queries
those are sent to `1.1.1.1:53`, but all other queries are sent to `8.8.8.8:53`. those are sent to `1.1.1.1:53`, but all other queries are sent to `8.8.8.8:53`.
* A configuration like:
```none
8.8.8.8:53
[/host.com/]1.1.1.1:53 2.2.2.2:53
```
sends queries for `*.host.com` to `1.1.1.1:53` and `2.2.2.2:53`, but all
other queries are sent to `8.8.8.8:53`.
### <a href="#upstreams-from-file" id="upstreams-from-file" name="upstreams-from-file">Loading upstreams from file</a> ### <a href="#upstreams-from-file" id="upstreams-from-file" name="upstreams-from-file">Loading upstreams from file</a>
Using specific upstreams for some domains is a common way to accelerate internet Using specific upstreams for some domains is a common way to accelerate internet