Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-11-02 02:03:13 -05:00
Code Issues Packages Projects Releases Wiki Activity

mw/*: updates docs about upstream (#968)

Browse Source 
Upstream allows file structured like /etc/resolv.conf. Update docs.

Fixes #709
This commit is contained in:
Miek Gieben
2017-08-22 14:56:00 +01:00
committed by GitHub
parent 5604568655
commit 60d5e71a1a
4 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
middleware/auto/README.md
View File

@@ -31,7 +31,8 @@ are used.
* `no_reload` by default CoreDNS will reload a zone from disk whenever it detects a change to the * `no_reload` by default CoreDNS will reload a zone from disk whenever it detects a change to the
file. This option disables that behavior. file. This option disables that behavior.
* `upstream` defines upstream resolvers to be used resolve external names found (think CNAMEs) * `upstream` defines upstream resolvers to be used resolve external names found (think CNAMEs)
pointing to external names. pointing to external names. **ADDRESS** can be an IP address, and IP:port or a string pointing to
a file that is structured as /etc/resolv.conf.
All directives from the *file* middleware are supported. Note that *auto* will load all zones found, 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: even though the directive might only receive queries for a specific zone. I.e:

3
middleware/file/README.md
View File

@@ -39,7 +39,8 @@ file DBFILE [ZONES... ] {
file. This option disables that behavior. file. This option disables that behavior.
* `upstream` defines upstream resolvers to be used resolve external names found (think CNAMEs) * `upstream` defines upstream resolvers to be used resolve external names found (think CNAMEs)
pointing to external names. This is only really useful when CoreDNS is configured as a proxy, for pointing to external names. This is only really useful when CoreDNS is configured as a proxy, for
normal authoritative serving you don't need *or* want to use this. normal authoritative serving you don't need *or* want to use this. **ADDRESS** can be an IP
address, and IP:port or a string pointing to a file that is structured as /etc/resolv.conf.
## Examples ## Examples

4
middleware/kubernetes/README.md
View File

@@ -24,10 +24,10 @@ kubernetes [ZONES...] {
resyncperiod DURATION resyncperiod DURATION
endpoint URL endpoint URL
tls CERT KEY CACERT tls CERT KEY CACERT
namespaces NAMESPACE [NAMESPACE...] namespaces NAMESPACE...
labels EXPRESSION labels EXPRESSION
pods POD-MODE pods POD-MODE
upstream ADDRESS [ADDRESS...] upstream ADDRESS...
fallthrough fallthrough
} }
``` ```

3
middleware/secondary/README.md
View File

@@ -26,7 +26,8 @@ secondary [zones...] {
* `transfer to` can be enabled to allow this secondary zone to be transferred again. * `transfer to` can be enabled to allow this secondary zone to be transferred again.
* `upstream` defines upstream resolvers to be used resolve external names found (think CNAMEs) * `upstream` defines upstream resolvers to be used resolve external names found (think CNAMEs)
pointing to external names. This is only really useful when CoreDNS is configured as a proxy, for pointing to external names. This is only really useful when CoreDNS is configured as a proxy, for
normal authoritative serving you don't need *or* want to use this. normal authoritative serving you don't need *or* want to use this. **ADDRESS** can be an IP
address, and IP:port or a string pointing to a file that is structured as /etc/resolv.conf.
## Examples ## Examples