From f315950c916cdf92b27f13d334a3e4e5e56b2035 Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Thu, 31 Aug 2023 14:14:10 -0500 Subject: [PATCH] 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> --- website/content/docs/enterprise/admin-partitions.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/website/content/docs/enterprise/admin-partitions.mdx b/website/content/docs/enterprise/admin-partitions.mdx index 023e38ee31..74f7d64f01 100644 --- a/website/content/docs/enterprise/admin-partitions.mdx +++ b/website/content/docs/enterprise/admin-partitions.mdx @@ -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