Files
coredns/middleware/file
Miek Gieben dcd05032a4 Watch the entire directory
Instead of watching a single file watch the entire directory and
catch the .Name from the event. On any event, just reload the damn
thing. This also fixes the problem of loosing events when the inode
changes.
2016-04-15 20:00:17 +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-02 17:49:13 +01:00
2016-04-14 07:33:03 +01:00
2016-04-15 17:08:31 +01:00
2016-03-28 18:23:17 +01:00
2016-04-06 22:29:33 +01:00
2016-04-15 20:00:17 +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 from [address...]
    transfer to [address...]
    no_reload
}
  • transfer enables zone transfers. It may be specified multiples times. To or from signals the direction. Addresses must be denoted in CIDR notation (127.0.0.1/32 etc.) or just as plain address. The special wildcard "*" means: the entire internet (only valid for 'transfer to').
  • no_reload by default CoreDNS will reload a zone from disk whenever it detects a change to the file. This option disables that behavior.

Examples

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

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