2016-03-27 07:37:23 +01:00
|
|
|
# file
|
|
|
|
|
|
|
|
|
|
`file` enabled reading zone data from a RFC-1035 styled file.
|
|
|
|
|
|
|
|
|
|
The etcd middleware makes extensive use of the proxy middleware to forward and query
|
|
|
|
|
other servers in the network.
|
|
|
|
|
|
|
|
|
|
## Syntax
|
|
|
|
|
|
|
|
|
|
~~~
|
|
|
|
|
file dbfile [zones...]
|
|
|
|
|
~~~
|
|
|
|
|
|
|
|
|
|
* `dbfile` the database file to read and parse.
|
|
|
|
|
* `zones` zones it should be authoritative for. If empty the zones from the configuration block
|
|
|
|
|
are used.
|
|
|
|
|
|
2016-03-28 12:08:05 +01:00
|
|
|
If you want to round robin A and AAAA responses look at the `loadbalance` middleware.
|
2016-03-27 07:37:23 +01:00
|
|
|
|
2016-04-03 07:37:41 +01:00
|
|
|
TSIG key configuration is TODO; directive format will change.
|
|
|
|
|
|
2016-03-27 07:37:23 +01:00
|
|
|
~~~
|
2016-03-28 12:08:05 +01:00
|
|
|
file dbfile [zones... ] {
|
2016-04-03 07:37:41 +01:00
|
|
|
transfer out [address...]
|
2016-03-27 07:37:23 +01:00
|
|
|
}
|
|
|
|
|
~~~
|
|
|
|
|
|
2016-03-28 12:08:05 +01:00
|
|
|
* `transfer` enable zone transfers, for now only `transfer out` does something. It enables outgoing
|
|
|
|
|
zone transfers when defined.
|
2016-03-27 07:37:23 +01:00
|
|
|
|
|
|
|
|
## Examples
|