mirror of
https://github.com/coredns/coredns.git
synced 2025-11-12 06:52:24 -05:00
9fb266aebe
Fix transferring the zone from a master and the matching of notifies to source and dst IP addresses. Add `upstream` keyword as well, because it is needed for the same reasons as in the *file* middlware. Add some dire warning about upstream in the readme of both middlewares. Out of band testing, hidden by net build tag was added. Integration testing still needs to be setup.
39 lines
1.0 KiB
Markdown
39 lines
1.0 KiB
Markdown
# 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 from` specifies from which address to fetch the zone. It can be specified multiple times;
|
|
if one does not work, another will be tried.
|
|
* `transfer to` can be enabled to allow this secondary zone to be transferred again.
|
|
* `upstream` defines 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
|
|
}
|
|
~~~
|