aboutsummaryrefslogtreecommitdiff
path: root/man/coredns-tls.7
diff options
context:
space:
mode:
Diffstat (limited to 'man/coredns-tls.7')
-rw-r--r--man/coredns-tls.79
1 files changed, 3 insertions, 6 deletions
diff --git a/man/coredns-tls.7 b/man/coredns-tls.7
index 945c15925..5da73e2dc 100644
--- a/man/coredns-tls.7
+++ b/man/coredns-tls.7
@@ -1,7 +1,7 @@
.\" generated with Ronn/v0.7.3
.\" http://github.com/rtomayko/ronn/tree/0.7.3
.
-.TH "COREDNS\-TLS" "7" "October 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-TLS" "7" "March 2019" "CoreDNS" "CoreDNS plugins"
.
.SH "NAME"
\fItls\fR \- allows you to configure the server certificates for the TLS and gRPC servers\.
@@ -10,9 +10,6 @@
CoreDNS supports queries that are encrypted using TLS (DNS over Transport Layer Security, RFC 7858) or are using gRPC (https://grpc\.io/, not an IETF standard)\. Normally DNS traffic isn\'t encrypted at all (DNSSEC only signs resource records)\.
.
.P
-The \fIproxy\fR plugin also support gRPC (\fBprotocol gRPC\fR), meaning you can chain CoreDNS servers using this protocol\.
-.
-.P
The \fItls\fR "plugin" allows you to configure the cryptographic keys that are needed for both DNS\-over\-TLS and DNS\-over\-gRPC\. If the \fBtls\fR directive is omitted, then no encryption takes place\.
.
.P
@@ -38,7 +35,7 @@ Start a DNS\-over\-TLS server that picks up incoming DNS\-over\-TLS queries on p
tls://\.:5553 {
tls cert\.pem key\.pem ca\.pem
- proxy \. /etc/resolv\.conf
+ forward \. /etc/resolv\.conf
}
.
.fi
@@ -54,7 +51,7 @@ Start a DNS\-over\-gRPC server that is similar to the previous example, but usin
grpc://\. {
tls cert\.pem key\.pem ca\.pem
- proxy \. /etc/resolv\.conf
+ forward \. /etc/resolv\.conf
}
.
.fi