From a2205318ff493beb445a45b40e7748da2b0e0fa6 Mon Sep 17 00:00:00 2001 From: Konstantine Date: Thu, 2 Dec 2021 22:39:02 +0200 Subject: [PATCH] Update website/content/docs/discovery/dns.mdx Co-authored-by: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com> --- website/content/docs/discovery/dns.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/content/docs/discovery/dns.mdx b/website/content/docs/discovery/dns.mdx index a3db818f4f..d26e95c86a 100644 --- a/website/content/docs/discovery/dns.mdx +++ b/website/content/docs/discovery/dns.mdx @@ -107,7 +107,9 @@ external queries by using different domains. Consul versions 1.5.2+ can be configured to respond to DNS queries on an alternative domain through the [`alt_domain`](/docs/agent/options#alt_domain) agent configuration -option. Consul's DNS response will use the same domain as was used in the query. +option. As of Consul versions 1.11.0+, Consul's DNS response will use the same domain as was used in the query; +in prior versions, the response may use the primary [`domain`](/docs/agent/options#domain) no matter which +domain was used in the query. For example, if `test-domain` is configured as the alternative domain, the following query: ```shell-session