# Scope Use DNS Policy for Geo-Location Based Traffic Management with Primary Servers in observed AD/DNS state > Use Use DNS Policy for Geo-Location Based Traffic Management with Primary Servers to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/scope-use-dns-policy-for-geo-location-based-traffic-management-with-primary-servers-in-observed-ad/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:05:45+00:00 - Modified: 2026-08-27T17:14:53+00:00 - Last reviewed by DSE: 2026-08-27 - Resource type: Briefing - DSE priority: Advisory - Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Use DNS Policy for Geo-Location Based Traffic Management with Primary Servers to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of Use DNS Policy for Geo-Location Based Traffic Management with Primary Servers ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Use this document to resolve one bounded operational decision: Scope Use DNS Policy for Geo-Location Based Traffic Management with Primary Servers in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Use DNS Policy for Geo-Location Based Traffic Management with Primary Servers](https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/primary-geo-location) from Microsoft supports the following bounded statements: - At Introduction below H1, Microsoft states: “Important: This scenario illustrates how to deploy DNS policy for geo-location based traffic management when you are using only primary DNS servers.” The research record locates this support at Introduction below H1. - At Introduction below H1, Microsoft states: “You can also accomplish geo-location based traffic management when you have both primary and secondary DNS servers.” The research record locates this support at Introduction below H1. These statements are the factual basis for this document. Do not extend them into a broader assurance. Review Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles only where the source and recorded environment align. ## What the source does not establish The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution, ownership, and change authority instead of treating documented behavior as a deployment guarantee. ## Applicability questions - For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here? - Within Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, which versions, roles, and configuration states define the review population? - Could Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution invalidate the test, hide a failure, or change applicability? - Who owns the decision, and which observation requires stopping, escalation, or rollback? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation. Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution. Handle credentials, keys, recovery data, and personal information through approved secure channels. ## Verification and evidence Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Introduction below H1; Introduction below H1. Favor PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands, linked to stable identifiers, time, and operator. Label this evidence set DSE-20260827-101 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review. Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes. ## Official references - [Use DNS Policy for Geo-Location Based Traffic Management with Primary Servers](https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/primary-geo-location) — Microsoft ## Primary reference - Name: Use DNS Policy for Geo-Location Based Traffic Management with Primary Servers - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/primary-geo-location - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Scope Use DNS Policy for Geo-Location Based Traffic Management with Primary Servers in observed AD/DNS state,” DSE Security, https://update.dsesecurity.com/updates/scope-use-dns-policy-for-geo-location-based-traffic-management-with-primary-servers-in-observed-ad/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.