From 9802af7bdce5a43f2eedae88530530af66bcd401 Mon Sep 17 00:00:00 2001
From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com>
Date: Wed, 13 May 2026 16:04:24 +0200
Subject: [PATCH] docs: rename DNS wildcard routing to routing peer DNS
 resolution (#745)

Matches the dashboard rename. The setting moves DNS resolution for
routed domains from the client to the routing peer; wildcard routing
is one consequence rather than the primary purpose, so the canonical
section now leads with that framing.

Heading anchor changes from #enable-dns-wildcard-routing to
#enable-routing-peer-dns-resolution. Keeps an invisible legacy anchor
on both pages so external bookmarks still scroll to the section.
---
 src/pages/manage/networks/how-routing-peers-work.mdx |  2 +-
 src/pages/manage/networks/index.mdx                  | 12 ++++++------
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/src/pages/manage/networks/how-routing-peers-work.mdx b/src/pages/manage/networks/how-routing-peers-work.mdx
index 67ad0614..b5f947d1 100644
--- a/src/pages/manage/networks/how-routing-peers-work.mdx
+++ b/src/pages/manage/networks/how-routing-peers-work.mdx
@@ -167,7 +167,7 @@ The Management service only flips an account to 22054 once every peer is on 0.59
 
 ### Routing Peer DNS Resolution
 
-Wildcard domain resources require [Routing Peer DNS Resolution](/manage/networks#enable-dns-wildcard-routing) to be enabled. With this setting on, DNS resolution happens on the routing peer rather than on the client.
+Wildcard domain resources require [Routing Peer DNS Resolution](/manage/networks#enable-routing-peer-dns-resolution) to be enabled. With this setting on, DNS resolution happens on the routing peer rather than on the client.
 
 ### Pitfall: domains and IP ranges in the same network
 
diff --git a/src/pages/manage/networks/index.mdx b/src/pages/manage/networks/index.mdx
index 285ccadd..2c09a297 100644
--- a/src/pages/manage/networks/index.mdx
+++ b/src/pages/manage/networks/index.mdx
@@ -68,7 +68,7 @@ Resources are the machines, services, or subnets you want to access within your
 - Single IP addresses
 - IP ranges
 - Domain names (e.g., `example.com`)
-- Wildcard domains (e.g., `*.company.internal`) when [DNS wildcard routing](#enable-dns-wildcard-routing) is enabled
+- Wildcard domains (e.g., `*.company.internal`) when [routing peer DNS resolution](#enable-routing-peer-dns-resolution) is enabled
 
 <p>
     <img src="/docs-static/img/manage/networks/index/resources-1.png" alt="resources" className="imagewrapper-big"/>
@@ -170,24 +170,24 @@ This additional policy ensures that the routing peer's input chain allows inboun
     This is a common pitfall when the routing peer also runs local services. Remember: network resource policies control forwarded traffic (forward chain), while peer-to-peer access control policies control traffic to the peer itself (input chain). You need both if you want to access the routing peer **and** the resources behind it.
 </Note>
 
-## Enable DNS Wildcard Routing
+<div id="enable-dns-wildcard-routing" />
 
-To use wildcard domains as resources, you must enable DNS wildcard routing. This setting changes how domains are resolved: instead of the client resolving domains locally, the routing peer performs DNS resolution.
+## Enable Routing Peer DNS Resolution
 
-This is also useful for regular domain resources when you want to:
+Routing peer DNS resolution moves DNS resolution for routed domains from the client to the routing peer. Wildcard domain resources require it; for regular domain resources, enable it when you want to:
 
 - Resolve domain names using the routing peer's DNS infrastructure
 - Route traffic through a geographically nearby routing peer
 - Enable more restrictive access control rules (support coming in future releases)
 
-To enable DNS wildcard routing, go to **Settings** > **Networks** > **Enable DNS wildcard routing**:
+To enable it, go to **Settings** > **Networks** > **Enable Routing peer DNS resolution**:
 
 <p>
     <img src="/docs-static/img/manage/networks/index/settings-1.png" alt="settings-acl" className="imagewrapper-big"/>
 </p>
 
 <Note>
-    DNS wildcard routing requires routing peers and clients running version 0.35.0 or later. After enabling this feature, restart your routing peers and clients to apply the changes.
+    Routing peer DNS resolution requires routing peers and clients running version 0.35.0 or later. After enabling this feature, restart your routing peers and clients to apply the changes.
 </Note>
 
 <Note>