TrueCloudLab/coredns
16
0
Fork 2
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

plugin/forward: fix descriptions in README.md (#6123)

Browse source 
Signed-off-by: Justin <cattyhouse@users.noreply.github.com>
This commit is contained in:
Justin 2023-05-27 05:01:06 +08:00 • committed by GitHub
parent a4c34d0573
commit 7231bb0881
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
plugin/forward/README.md
View file

@ -97,7 +97,7 @@ forward FROM TO... {
As an upper bound for **MAX**, consider that each concurrent query will use about 2kb of memory. 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 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: 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 { .: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 tls_servername dns.google
} }
} }
.:5302 { .: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 tls_servername cloudflare-dns.com
} }
} }