From bd136d12dc5746b876b0177f336feec8b0b9c4c5 Mon Sep 17 00:00:00 2001
From: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com>
Date: Tue, 29 Aug 2023 19:57:03 -0400
Subject: [PATCH] docs: admin partition and DNS clarification

---
 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..9d5a073e99 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.
+The DNS interface returns results for a single admin partition.
+The query may explicitly specify the admin partition to use in the lookup.
+If no admin partition is specified in the query,
+the lookup uses the admin partition of the Consul agent acting as the DNS server.
+Server agents always exist within the `default` admin partition.
+Client agents are configured to operate within a specific admin partition.
 
 ### Service Mesh Configurations