mirror of https://github.com/coredns/coredns.git synced 2025-10-27 08:14:18 -04:00

Files

Miek Gieben 219bfd0493 middleware/metrics: cleanup (#355 )

* 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

2016-10-26 10:01:52 +01:00

auto.go

middleware/metrics: cleanup (#355 )

2016-10-26 10:01:52 +01:00

README.md

middleware/auto: add (#333 )

2016-10-17 18:37:56 +01:00

regexp_test.go

middleware/auto: add (#333 )

2016-10-17 18:37:56 +01:00

regexp.go

middleware/auto: add (#333 )

2016-10-17 18:37:56 +01:00

setup_test.go

middleware/auto: add (#333 )

2016-10-17 18:37:56 +01:00

setup.go

middleware/metrics: cleanup (#355 )

2016-10-26 10:01:52 +01:00

walk_test.go

middleware/metrics: cleanup (#355 )

2016-10-26 10:01:52 +01:00

walk.go

middleware/metrics: cleanup (#355 )

2016-10-26 10:01:52 +01:00

watcher_test.go

middleware/metrics: cleanup (#355 )

2016-10-26 10:01:52 +01:00

zone.go

middleware/metrics: cleanup (#355 )

2016-10-26 10:01:52 +01:00

README.md

auto

auto enables serving zone data from an RFC 1035-style master file which is automatically picked up from disk.

The auto 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. New zones or changed zone are automatically picked up from disk.

Syntax

auto [ZONES...] {
    directory DIR [REGEXP ORIGIN_TEMPLATE [TIMEOUT]]
}

ZONES zones it should be authoritative for. If empty, the zones from the configuration block are used.

directory loads zones from the speficied DIR. If a file name matches REGEXP it will be used to extract the origin. ORIGIN_TEMPLATE will be used as a template for the origin. Strings like {<number>} are replaced with the respective matches in the file name, i.e. {1} is the first match, {2} is the second, etc.. The default is: db\.(.*) {1} e.g. from a file with the name db.example.com, the extracted origin will be example.com. TIMEOUT specifies how often CoreDNS should scan the directory, the default is every 60 seconds. This value is in seconds. The minimum value is 1 second.

All directives from the file middleware are supported. Note that auto will load all zones found, even though the directive might only receive queries for a specific zone. I.e:

auto example.org {
    directory /etc/coredns/zones
}

Will happily pick up a zone for example.COM, except it will never be queried, because the auto directive only is authoritative for example.ORG.

Examples

Load org domains from /etc/coredns/zones/org and allow transfers to the internet, but send notifies to 10.240.1.1

auto org {
    directory /etc/coredns/zones/org
    transfer to *
    transfer to 10.240.1.1
}

Load org domains from /etc/coredns/zones/org and looks for file names as www.db.example.org, where example.org is the origin. Scan every 45 seconds.

auto org {
    directory /etc/coredns/zones/org www\.db\.(.*) {1} 45
}