Update website/content/docs/discovery/dns.mdx

Co-authored-by: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com>
This commit is contained in:
Konstantine 2021-11-22 01:14:19 +02:00 committed by GitHub
parent eb21aab1b5
commit 2900f3861a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 3 deletions

View File

@ -98,10 +98,16 @@ node's metadata key starts with `rfc1035-`.
## Alternative Domain ## Alternative Domain
Consul support setting an alternative domain, which is usefull during DNS migrations or if you want to respond to By default, Consul responds to DNS queries only for its configured
internal and external queries with different domains. [`domain`](/docs/agent/options#domain).
If you are using [`alt_domain`](/docs/agent/options#alt_domain) parameter, Consul will respond based on the presence of it in your queries. Some use cases require responding to queries for more than one domain,
such as during a DNS migration or to distinguish between internal and
external queries by using different domains.
Consul can 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.
For example, if `test-domain` is configured as the alternative domain, the following query: For example, if `test-domain` is configured as the alternative domain, the following query:
```shell-session ```shell-session