plugin.cfg

# Directives are registered in the order they should be executed.
#
# Ordering is VERY important. Every plugin will feel the effects of all other
# plugin below (after) them during a request, but they must not care what plugin
# above them are doing.

# How to rebuild with updated plugin configurations: Modify the list below and
# run `go generate && go build`

# The parser takes the input format of:
#
#     <plugin-name>:<package-name>
# Or
#     <plugin-name>:<fully-qualified-package-name>
#
# External plugin example:
#
# log:github.com/coredns/coredns/plugin/log
# Local plugin example:
# log:log

metadata:metadata
cancel:cancel
tls:tls
reload:reload
nsid:nsid
bufsize:bufsize
root:root
bind:bind
debug:debug
#trace:trace
ready:ready
health:health
pprof:pprof
#prometheus:metrics
errors:errors
log:log
#dnstap:dnstap
local:local
#dns64:dns64
acl:acl
any:any
#chaos:chaos
loadbalance:loadbalance
cache:cache
rewrite:rewrite
dnssec:dnssec
#autopath:autopath
template:template
transfer:transfer
hosts:hosts
#route53:route53
#azure:azure
#clouddns:clouddns
#k8s_external:k8s_external
#kubernetes:kubernetes
file:file
auto:auto
secondary:secondary
#etcd:etcd
#loop:loop
forward:forward
#grpc:grpc
#erratic:erratic
#whoami:whoami
on:github.com/coredns/caddy/onevent
sign:sign
meshname:github.com/zhoreeq/coredns-meshname
meship:github.com/zhoreeq/coredns-meship