From 0db9346ecc649d2bef3bbff1cbb7881aa0637338 Mon Sep 17 00:00:00 2001 From: Marc Tamsky Date: Fri, 28 Aug 2015 18:27:26 -0700 Subject: [PATCH] Explain 'recursors' behavior with an example. --- website/source/docs/guides/forwarding.html.markdown | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/website/source/docs/guides/forwarding.html.markdown b/website/source/docs/guides/forwarding.html.markdown index 856fa59645..809c4f68e9 100644 --- a/website/source/docs/guides/forwarding.html.markdown +++ b/website/source/docs/guides/forwarding.html.markdown @@ -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, but this is not required. -Additionally, by default, consul will not attempt to resolve CNAME records outside the `.consul.` -zone, unless the [recursors](/docs/agent/options.html#recursors) configuration -option is set. +It is worth mentioning that, by default, consul does not resolve DNS +records outside the `.consul.` zone, unless the +[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