Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-10-27 08:14:18 -04:00
Code Issues Packages Projects Releases Wiki Activity

plugin/forward: clarify relation with proxy (#1747)

Browse Source 
some other small bits as well.
This commit is contained in:
Miek Gieben
2018-04-27 14:24:58 +01:00
committed by GitHub
parent 47b2b10209
commit f0f80ed739
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
plugin/forward/README.md
View File

@@ -21,6 +21,10 @@ connect to a random upstream (which may or may not work).
This plugin can only be used once per Server Block.
How does *forward* relate to *proxy*? This plugin is the "new" version of *proxy* and is faster
because it re-uses connections to the upstreams. It also does in-band health checks - using DNS
instead of HTTP. Since it is newer it has a little less (production) millage on it.
## Syntax
In its most basic form, a simple forwarder uses this syntax:
@@ -96,7 +100,7 @@ IPv6).
## Examples
Proxy all requests within example.org. to a nameserver running on a different port:
Proxy all requests within `example.org.` to a nameserver running on a different port:
~~~ corefile
example.org {
@@ -149,7 +153,7 @@ service with health checks.
## Bugs
The TLS config is global for the whole forwarding proxy if you need a different `tls_serveraame` for
The TLS config is global for the whole forwarding proxy if you need a different `tls_servername` for
different upstreams you're out of luck.
## Also See