docs: Reorganize DNS documentation (#635)

- Create Internal DNS Servers page consolidating nameserver configuration,
  private DNS routing, and Active Directory guidance
- Trim DNS Overview, DNS Settings removing duplicated and filler content
- Merge Configuring Nameservers page into Internal DNS Servers
- Replace Quickstart and Configuring Nameservers pages with redirects
- Update navigation sidebar and all internal links
This commit is contained in:
Jack Carter
2026-02-23 17:05:11 +01:00
committed by GitHub
parent e80b6b522a
commit a87e560602
10 changed files with 256 additions and 1074 deletions
+4
View File
@@ -87,6 +87,10 @@ For troubleshooting, see [Debugging access to Domain Resources](/help/troublesho
Firewall blocking DNS requests is the most common cause of domain resource issues.
</Note>
<Note>
When a routing peer cannot resolve a domain resource (e.g., an internal domain like `fileserver.corp.local`), you may need to configure a [Nameserver](/manage/dns/internal-dns-servers#configuring-nameservers-for-internal-domains) for your internal DNS and add the routing peer's group as a distribution group. See [Internal DNS Servers](/manage/dns/internal-dns-servers#domain-resources-and-routing-peer-dns) for details.
</Note>
## Manage Access to Resources
To control access to resources, assign them to groups and create [access control policies](/manage/access-control/manage-network-access#creating-policies). A peer can only see a resource when a policy grants access from one of the peer's groups (source) to one of the resource's groups (destination).