diff options
| author |  Miek Gieben <miek@miek.nl>
| 2018-04-27 14:24:58 +0100 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2018-04-27 14:24:58 +0100 |
| commit | f0f80ed739bed8dbf2b707370958b51074cd11f3 (patch) | |
| tree | 0660070ff657254935e661127a5cc21e3741176d /plugin | |
| parent | 47b2b102091db3ca3fb67761d7952a9723da08ff (diff) | |
| download | coredns-f0f80ed739bed8dbf2b707370958b51074cd11f3.tar.gz coredns-f0f80ed739bed8dbf2b707370958b51074cd11f3.tar.zst coredns-f0f80ed739bed8dbf2b707370958b51074cd11f3.zip | |
plugin/forward: clarify relation with proxy (#1747)
some other small bits as well.
Diffstat (limited to 'plugin')
| -rw-r--r-- | plugin/forward/README.md | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/plugin/forward/README.md b/plugin/forward/README.md index c4e383fd4..6b1a1b6c0 100644 --- a/plugin/forward/README.md +++ b/plugin/forward/README.md @@ -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 |