Backport of docs: admin partition and DNS clarification into release/1.16.x (#18633)

* backport of commit bd136d12dc5746b876b0177f336feec8b0b9c4c5

* backport of commit cb770fa67d6d0dd38641674c108d99f5914f08b4

---------

Co-authored-by: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com>
This commit is contained in:
hc-github-team-consul-core 2023-08-31 14:14:10 -05:00 committed by GitHub
parent 523957a881
commit f04738b4e7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 1 deletions

View File

@ -53,7 +53,12 @@ Only resources in the `default` admin partition will be replicated to secondary
### DNS Queries
Client agents will be configured to operate within a specific admin partition. The DNS interface will only return results for the admin partition within the scope of the client.
When queried, the DNS interface returns results for a single admin partition.
The query may explicitly specify the admin partition to use in the lookup.
If you do not specify an admin partition in the query,
the lookup uses the admin partition of the Consul agent that received the query.
Server agents always exist within the `default` admin partition.
Client agents are configured to operate within a specific admin partition.
### Service Mesh Configurations