mirror of
https://github.com/coredns/coredns.git
synced 2025-11-01 10:43:17 -04:00
bfaf9e0aec
* core: add listening for other protocols
Allow CoreDNS to listen for TLS request coming over port 853. This can
be enabled with `tls://` in the config file.
Implement listening for grps:// as well.
a Corefile like:
~~~
. tls://.:1853 {
whoami
tls
}
~~~
Means we listen on 1853 for tls requests, the `tls` config item allows
configuration for TLS parameters. We *might* be tempted to use Caddy's
Let's Encrypt implementation here.
* Refactor coredns/grpc into CoreDNS
This makes gRPC a first class citizen in CoreDNS. Add defines as being
just another server.
* some cleanups
* unexport the servers
* Move protobuf dir
* Hook up TLS properly
* Fix test
* listen for TLS as well. README updates
* disable test, fix package
* fix test
* Fix tests
* Fix remaining test
* Some tests
* Make the test work
* Add grpc test from #580
* fix crash
* Fix tests
* Close conn
* README cleanups
* README
* link RFC
38 lines
627 B
Go
38 lines
627 B
Go
// generated by directives_generate.go; DO NOT EDIT
|
|
|
|
package dnsserver
|
|
|
|
// Directives are registered in the order they should be
|
|
// executed.
|
|
//
|
|
// Ordering is VERY important. Every middleware will
|
|
// feel the effects of all other middleware below
|
|
// (after) them during a request, but they must not
|
|
// care what middleware above them are doing.
|
|
|
|
var directives = []string{
|
|
"tls",
|
|
"root",
|
|
"bind",
|
|
"trace",
|
|
"health",
|
|
"pprof",
|
|
"prometheus",
|
|
"errors",
|
|
"log",
|
|
"chaos",
|
|
"cache",
|
|
"rewrite",
|
|
"loadbalance",
|
|
"dnssec",
|
|
"reverse",
|
|
"file",
|
|
"auto",
|
|
"secondary",
|
|
"etcd",
|
|
"kubernetes",
|
|
"proxy",
|
|
"whoami",
|
|
"erratic",
|
|
}
|