mirror of
https://github.com/coredns/coredns.git
synced 2025-09-20 21:21:30 +02:00
Changes large parts of proxy lookup mechanism. The duplicate zone checking erroneous added a nameserver for each zone we are auth. for, creating to many backend hosts. So even when a host was determined do be Down() we still got an (identical) new one from the list. The Down() and failure checking for upstream hosts had data race in the uh.Fails check - we now use atomic.LoadInt32 for that. Use and debug the test/server.go test servers implementation in the TestStubLookup test to prevent going out to the internet. Also delete the stub cycle test. That test was wrong and did not test what it needed to be testing. Deleted for now.
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 *
}