aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Justin <cattyhouse@users.noreply.github.com> 2023-05-27 05:01:06 +0800
committerGravatar GitHub <noreply@github.com> 2023-05-26 17:01:06 -0400
commit7231bb0881831fa8eac55b4ea34fc579cba3f43d (patch)
tree45a7f5ce4b277317d4b9ea5e605222e088aaea21
parenta4c34d0573db43b0ed9ef709e9fa22cd752bdfb0 (diff)
downloadcoredns-7231bb0881831fa8eac55b4ea34fc579cba3f43d.tar.gz
coredns-7231bb0881831fa8eac55b4ea34fc579cba3f43d.tar.zst
coredns-7231bb0881831fa8eac55b4ea34fc579cba3f43d.zip
plugin/forward: fix descriptions in README.md (#6123)
Signed-off-by: Justin <cattyhouse@users.noreply.github.com>
-rw-r--r--plugin/forward/README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/plugin/forward/README.md b/plugin/forward/README.md
index 0088c9c7c..ab2ef2b4b 100644
--- a/plugin/forward/README.md
+++ b/plugin/forward/README.md
@@ -97,7 +97,7 @@ forward FROM TO... {
As an upper bound for **MAX**, consider that each concurrent query will use about 2kb of memory.
Also note the TLS config is "global" for the whole forwarding proxy if you need a different
-`tls-name` for different upstreams you're out of luck.
+`tls_servername` for different upstreams you're out of luck.
On each endpoint, the timeouts for communication are set as follows:
@@ -248,13 +248,13 @@ Or when you have multiple DoT upstreams with different `tls_servername`s, you ca
}
.:5301 {
- forward . 8.8.8.8 8.8.4.4 {
+ forward . tls://8.8.8.8 tls://8.8.4.4 {
tls_servername dns.google
}
}
.:5302 {
- forward . 1.1.1.1 1.0.0.1 {
+ forward . tls://1.1.1.1 tls://1.0.0.1 {
tls_servername cloudflare-dns.com
}
}