219bfd0493
* middleware/metrics: add more metrics middleware/cache: Add metrics for number of elements in the cache. Also export the total size. Update README to detail the new metrics. middleware/metrics Move metrics into subpackage called "vars". This breaks the import cycle and is cleaner. This allows vars.Report to be used in the the dnsserver to log refused queries. middleware/metrics: tests Add tests to the metrics framework. The metrics/test subpackage allows scraping of the local server. Do a few test scrape of the metrics that are defined in the metrics middleware. This also allows metrics integration tests to check if the caching and dnssec middleware export their metrics correctly. * update README * typos * fix tests
file
file enables serving zone data from an RFC 1035-style master file.
The file middleware is used for an "old-style" DNS server. It serves from a preloaded file that exists on disk. If the zone file contains signatures (i.e. is signed, i.e. DNSSEC) correct DNSSEC answers are returned. Only NSEC is supported! If you use this setup you are responsible for resigning the zonefile.
Syntax
file DBFILE [ZONES...]
- DBFILE the database file to read and parse. If the path is relative the path from the root directive will be prepended to it.
- 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[:ALG]] [BASE64]
file DBFILE [ZONES... ] {
transfer to ADDRESS...
no_reload
}
transferenables zone transfers. It may be specified multiples times.Toorfromsignals the direction. ADDRESS must be denoted in CIDR notation (127.0.0.1/32 etc.) or just as plain addresses. The special wildcard*means: the entire internet (only valid for 'transfer to'). When an address is specified a notify message will be send whenever the zone is reloaded.no_reloadby default CoreDNS will reload a zone from disk whenever it detects a change to the file. This option disables that behavior.
Examples
Load the example.org zone from example.org.signed and allow transfers to the internet, but send
notifies to 10.240.1.1
file example.org.signed example.org {
transfer to *
transfer to 10.240.1.1
}