status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Explain 'recursors' behavior with an example.

This commit is contained in:
Marc Tamsky 2015-08-28 18:27:26 -07:00
parent b71a51e277
commit 0db9346ecc
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/source/docs/guides/forwarding.html.markdown
View File

@ -18,9 +18,15 @@ as well as [dnsmasq](http://www.thekelleys.org.uk/dnsmasq/doc.html).
For the sake of simplicity, BIND and Consul are running on the same machine in this example, For the sake of simplicity, BIND and Consul are running on the same machine in this example,
but this is not required. but this is not required.
Additionally, by default, consul will not attempt to resolve CNAME records outside the `.consul.` It is worth mentioning that, by default, consul does not resolve DNS
zone, unless the [recursors](/docs/agent/options.html#recursors) configuration records outside the `.consul.` zone, unless the
option is set. [recursors](/docs/agent/options.html#recursors) configuration option
has been set. An example of how this changes consul's behavior is:
When a consul DNS reply includes a CNAME record pointing outside
`.consul.` the DNS reply includes only CNAME records.
Contrastingly, when `recursors` is set and the upstream resolver is
functioning correctly, consul will try to resolve CNAMEs and include
any A/PTR records for them in its DNS reply.
### BIND Setup ### BIND Setup