README
¶
auto
Name
auto - enables serving zone data from an RFC 1035-style master file, which is automatically picked up from disk.
Description
The auto plugin 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. using DNSSEC) correct DNSSEC answers are returned. Only NSEC is supported! If you use this setup you are responsible for re-signing the zonefile. New or changed zones are automatically picked up from disk.
Syntax
auto [ZONES...] {
directory DIR [REGEXP ORIGIN_TEMPLATE [TIMEOUT]]
reload DURATION
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 specified 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, e.g.{1}
is the first match,{2}
is the second. The default is:db\.(.*) {1}
i.e. from a file with the namedb.example.com
, the extracted origin will beexample.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.reload
interval to perform reload of zone if SOA version changes. Default is one minute. Value of0
means to not scan for changes and reload. eg.30s
checks zonefile every 30 seconds and reloads zone when serial changes.no_reload
deprecated. Sets reload to 0.upstream
defines upstream resolvers to be used resolve external names found (think CNAMEs) pointing to external names. ADDRESS can be an IP address, an IP:port or a string pointing to a file that is structured as /etc/resolv.conf. If no ADDRESS is given, CoreDNS will resolve CNAMEs against itself.
All directives from the file plugin 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.
org {
auto {
directory /etc/coredns/zones/org www\.db\.(.*) {1} 45
}
}
Documentation
¶
Overview ¶
Package auto implements an on-the-fly loading file backend.
Package auto implements a on-the-fly loading file backend.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Auto ¶
Auto holds the zones and the loader configuration for automatically loading zones.
type Zones ¶
type Zones struct { Z map[string]*file.Zone // A map mapping zone (origin) to the Zone's data. sync.RWMutex // contains filtered or unexported fields }
Zones maps zone names to a *Zone. This keep track of what we zones we have loaded at any one time.
func (*Zones) Add ¶
Add adds a new zone into z. If zo.NoReload is false, the reload goroutine is started.