Files
coredns/middleware/file
Miek Gieben 4829b40efa Rename middleware/testing (#103)
Rename to test and name the toplevel tests dir to test for consitency.
2016-04-11 07:56:38 +01:00
..
2016-04-02 17:49:13 +01:00
2016-04-02 17:49:13 +01:00
2016-04-02 17:49:13 +01:00
2016-04-11 07:56:38 +01:00
2016-04-02 16:56:16 +01:00
2016-04-09 16:17:53 +01:00
2016-04-02 17:49:13 +01:00
2016-04-07 08:03:57 +01:00
2016-04-03 09:02:34 +01:00
2016-04-06 22:29:33 +01:00
2016-03-28 18:23:17 +01:00
2016-04-09 16:39:50 +01:00
2016-04-06 22:29:33 +01:00
2016-04-07 07:42:58 +01:00

file

file enables serving zone data from a RFC-1035 styled file.

The file middleware is used for "old-style" DNS server. It serves from a preloaded file that exists on disk.

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.

If you want to round robin A and AAAA responses look at the loadbalance middleware.

TSIG key configuration is TODO; directive format for transfer will probably be extended with TSIG key information, something like transfer out [address] key [name] [base64]

file dbfile [zones... ] {
    transfer out [address...]
    transfer to [address]
}
  • transfer enables zone transfers. It may be specified multiples times. To or from signals the direction. Address must be denoted in CIDR notation (127.0.0.1/32 etc.). The special wildcard "*" means: the entire internet.

Examples

Load the miek.nl zone from miek.nl.signed and allow transfers to the internet.

file miek.nl.signed miek.nl {
    transfer to *
}