From 1dd187334b1657bf931cbd059b84482d82f619a7 Mon Sep 17 00:00:00 2001 From: Simon Zolin Date: Thu, 23 Apr 2020 15:22:24 +0300 Subject: [PATCH] - Specifying upstreams for domains: simplify ambiguous syntax description Squashed commit of the following: commit c78d163bd2ed973df22cda03c7c5168c7fb74ebf Author: Simon Zolin Date: Thu Apr 23 14:14:54 2020 +0300 - Specifying upstreams for domains: simplify ambiguous syntax description --- Configuration.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Configuration.md b/Configuration.md index c8fd973..6aa2db0 100644 --- a/Configuration.md +++ b/Configuration.md @@ -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. -**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!).