mirror of
https://github.com/coredns/coredns.git
synced 2025-10-27 00:04:15 -04:00
manpages: chop off first header (#2764)
each readme starts with the plugin's name as a header, this needs to be chopped off to provide a good manual page. Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
@@ -1,7 +1,6 @@
|
||||
.\" Generated by Mmark Markdown Processer - mmark.nl
|
||||
.TH "COREDNS-FORWARD" "7" "April 2019" "CoreDNS" "CoreDNS Plugins"
|
||||
|
||||
.SH FORWARD
|
||||
.SH NAME
|
||||
.PP
|
||||
\fIforward\fP - facilitates proxying DNS messages to upstream resolvers.
|
||||
@@ -26,11 +25,6 @@ connect to a random upstream (which may or may not work).
|
||||
.PP
|
||||
This plugin can only be used once per Server Block.
|
||||
|
||||
.PP
|
||||
How does \fIforward\fP relate to \fIproxy\fP? This plugin is the "new" version of \fIproxy\fP 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) mileage on it.
|
||||
|
||||
.SH SYNTAX
|
||||
.PP
|
||||
In its most basic form, a simple forwarder uses this syntax:
|
||||
|
||||
Reference in New Issue
Block a user