coredns/middleware/auto
Miek Gieben 52e01264e8 middleware/proxy: implement Exchanger (#480)
By defining and using an proxy.Exchanger interface we make the proxy
more generic and we can then fold back httproxy into proxy.

This overrides #463 and #473 and should make futures extensions rather
trivial

* Add docs that talk about `protocol` and how to set it.
* middleware/proxy: rename New to NewLookup
  It's used as a Lookup mechanism not as a completely new proxy,
  reflect that in the name.
* Set maxfails to 3 by default when looking up names.

Most of the changes have been copied
from https://github.com/johnbelamaric/coredns/pull/1/files
2017-01-15 08:12:58 +00:00
..
auto.go Add middleware.NextOrFailure (#462) 2016-12-20 18:58:05 +00:00
README.md middleware/{file, auto}: resolve external CNAMEs 2016-11-09 21:26:49 +00:00
regexp.go 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
setup.go middleware/proxy: implement Exchanger (#480) 2017-01-15 08:12:58 +00:00
setup_test.go Compile fixes and make it work 2016-11-10 12:58:40 +00:00
walk.go merge conflict fixed 2016-11-24 21:51:38 +01:00
walk_test.go middleware/auto: handle non-existent directory (#385) 2016-11-06 19:37:43 +00:00
watcher_test.go finish missing watcher check (#387) 2016-11-07 08:00:30 +00:00
zone.go middleware/metrics: cleanup (#355) 2016-10-26 10:01:52 +01:00

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]]
    no_reload
    upstream ADDRESS...
}

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.
  • no_reload by default CoreDNS will reload a zone from disk whenever it detects a change to the file. This option disables that behavior.
  • upstream defines upstream resolvers to be used resolve external names found (think CNAMEs) pointing to external names.

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
}