From fe5cbc6f5b89409dec60ef68626c67c87ce8d24c Mon Sep 17 00:00:00 2001 From: "coredns-auto-sync[bot]" Date: Tue, 15 Dec 2020 13:24:56 +0000 Subject: [PATCH] auto content sync --- content/plugins/forward.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/plugins/forward.md b/content/plugins/forward.md index abfcf98..9009b9c 100644 --- a/content/plugins/forward.md +++ b/content/plugins/forward.md @@ -4,7 +4,7 @@ description = "*forward* facilitates proxying DNS messages to upstream resolvers weight = 20 tags = ["plugin", "forward"] categories = ["plugin"] -date = "2020-11-03T14:42:34.87734811" +date = "2020-12-15T13:24:56.87756812" +++ ## Description @@ -91,7 +91,7 @@ forward FROM TO... { * `no_rec` - optional argument that sets the RecursionDesired-flag of the dns-query used in health checking to `false`. The flag is default `true`. * `max_concurrent` **MAX** will limit the number of concurrent queries to **MAX**. Any new query that would - raise the number of concurrent queries above the **MAX** will result in a SERVFAIL response. This + raise the number of concurrent queries above the **MAX** will result in a REFUSED response. This response does not count as a health failure. When choosing a value for **MAX**, pick a number at least greater than the expected *upstream query rate* * *latency* of the upstream servers. As an upper bound for **MAX**, consider that each concurrent query will use about 2kb of memory.