00f5c7797e
* mw/kubernetes: remove federation and cidr Remove both as we have a corefile syntax change that handles cidr and remove federation because that is going to be its own middleware. * backwards incompat changes This PR: * removes cidr from kubernetes (core Corefile feature now) * removes federation from kubernets (comes back as new middleware) * [remove autopath - which was already gone, so that already was backwards incompat] * adds `fallthrough` to the *etcd* middleware and makes you enable it. * Fail on unknown properties * documentation * Disable TestHealthCheck as it uses realtime and fails |
||
|---|---|---|
| .. | ||
| README.md | ||
| secondary.go | ||
| setup.go | ||
| setup_test.go | ||
secondary
secondary enables serving a zone retrieved from a primary server.
Syntax
secondary [ZONES...]
- ZONES zones it should be authoritative for. If empty, the zones from the configuration block are used. Note that without a remote address to get the zone from, the above is not that useful.
A working syntax would be:
secondary [zones...] {
transfer from ADDRESS
transfer to ADDRESS
upstream ADDRESS...
}
transfer fromspecifies from which address to fetch the zone. It can be specified multiple times; if one does not work, another will be tried.transfer tocan be enabled to allow this secondary zone to be transferred again.upstreamdefines upstream resolvers to be used resolve external names found (think CNAMEs) pointing to external names. This is only really useful when CoreDNS is configured as a proxy, for normal authoritative serving you don't need or want to use this.
Examples
secondary example.org {
transfer from 10.0.1.1
transfer from 10.1.2.1
}