Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-11-01 10:43:17 -04:00
Code Issues Packages Projects Releases Wiki Activity

Allow more than 1 address for transfer (#121)

Browse Source 
No reason why not to allow more then one address:
`transfer to 127.0.0.1 10.240.20.1`.

Fix startup as well, as it turned out to be broken...
This commit is contained in:
Miek Gieben
2016-04-14 19:57:39 +01:00
parent eb1f21bfff
commit 885e6e8246
4 changed files with 41 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
middleware/file/README.md
View File

@@ -18,18 +18,19 @@ file dbfile [zones...]
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]`
TSIG key information, something like `transfer out [address...] key [name] [base64]`
~~~
file dbfile [zones... ] {
transfer out [address...]
transfer to [address]
transfer from [address...]
transfer to [address...]
}
~~~
* `transfer` enables zone transfers. It may be specified multiples times. *To* or *from* signals
the direction. Address must be denoted in CIDR notation (127.0.0.1/32 etc.). The special
wildcard "*" means: the entire internet.
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').
## Examples