From 67fec9487ff9bdc811ba795e625b2380c3ee74ea Mon Sep 17 00:00:00 2001
From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com>
Date: Thu, 19 Feb 2026 16:30:09 +0100
Subject: [PATCH] docs: Add DNS guidance for Domain Controllers (#629)

Add use case for running NetBird on Windows Domain Controllers,
recommending a dedicated group with DNS management disabled to
avoid conflicts with Active Directory DNS services.
---
 src/pages/manage/dns/dns-settings.mdx | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/pages/manage/dns/dns-settings.mdx b/src/pages/manage/dns/dns-settings.mdx
index 5bcce679..48312c80 100644
--- a/src/pages/manage/dns/dns-settings.mdx
+++ b/src/pages/manage/dns/dns-settings.mdx
@@ -131,6 +131,16 @@ The peer will start using configured nameserver groups again.
 3. If fixed, investigate nameserver configuration
 4. If not fixed, issue is unrelated to NetBird DNS
 
+### Use Case 5: Domain Controllers
+
+**Problem**: Running NetBird on a Windows Domain Controller used as a routing peer can cause DNS conflicts, since Domain Controllers rely on their own DNS configuration for Active Directory services.
+
+**Solution**:
+1. Create a dedicated group for your Domain Controllers (e.g., "Domain Controllers")
+2. Go to **DNS** → **DNS Settings**
+3. Add the Domain Controller group to **Disable DNS management for these groups**
+4. Save Changes
+
 ---
 
 ## How Peers Behave in Each Mode