6e3eec1e72
If a README has a corefile snippet that is annotated with `corefile`,
this test will parse the instance and checks the snippet is legal.
This means a) we will get better docs b) we know for sure everything
still parses.
The test parses everything in middleware/*/README.md, it does not check
for README presence, just Corefile snippets. The port used is 10053 and
overrides whatever port is set in the docs.
The secondary middleware was used as an example and adds two examples
that should parse.
failures show up as:
~~~
--- FAIL: TestReadme (0.04s)
readme_test.go:50: Testing ../middleware/secondary/README.md, with 100 byte snippet
readme_test.go:50: Testing ../middleware/secondary/README.md, with 93 byte snippet
readme_test.go:53: Failed to start server for input "middleware/secondary: Corefile:3 - Error during parsing: unknown property 'transfeT'":
. {
secondary example.net {
transfeT from 10.1.2.1
transfer to *
}
}
FAIL
~~~
|
||
|---|---|---|
| .. | ||
| 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. ADDRESS can be an IP address, and IP:port or a string pointing to a file that is structured as /etc/resolv.conf.
Examples
Transfer example.org from 10.0.1.1, and if that fails try 10.1.2.1.
example.org {
secondary {
transfer from 10.0.1.1
transfer from 10.1.2.1
}
}
Or re-export the retrieved zone to other secondaries.
. {
secondary example.net {
transfer from 10.1.2.1
transfer to *
}
}