From beebafd906063335e461482998f372512af5912b Mon Sep 17 00:00:00 2001 From: Stanislav Chzhen Date: Fri, 27 Oct 2023 20:19:15 +0300 Subject: [PATCH] Pull request 185: 4977-multiple-domain-specific-upstreams Squashed commit of the following: commit dbfcf02ec1d547413831fd9f0d4fe7543ca6f2fe Author: Stanislav Chzhen Date: Wed Oct 25 20:35:40 2023 +0300 Configuration: multiple domain specific upstreams --- Configuration.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/Configuration.md b/Configuration.md index 8826491..cfe1dc4 100644 --- a/Configuration.md +++ b/Configuration.md @@ -117,6 +117,9 @@ The syntax is: [/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 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 @@ -202,6 +205,16 @@ upstreams. 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`. + * 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`. + ### Loading upstreams from file Using specific upstreams for some domains is a common way to accelerate internet