# Filter Windows DNS queries only with explicit match and timeout tests > Use Use DNS Policy for Applying Filters on DNS Queries to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/filter-windows-dns-queries-only-with-explicit-match-and-timeout-tests/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:15:31+00:00 - Modified: 2026-08-27T12:56:24+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Playbook - DSE priority: Advisory - Topics: Cybersecurity, IT, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Use DNS Policy for Applying Filters on DNS Queries 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 Applying Filters on DNS Queries ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Keep this document to one review outcome: Filter Windows DNS queries only with explicit match and timeout tests. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Use DNS Policy for Applying Filters on DNS Queries](https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/apply-filters-on-dns-queries) from Microsoft supports the following bounded statements: - Windows DNS Policy query filters can vary server behavior based on a query and the client that sent it. The research record locates this support at Article introduction. - Documented filter criteria include client subnet, transport, IP version, server interface, FQDN, query type, and time of day. The research record locates this support at Section ‘Query filter criteria’. 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 A DNS query filter is not a complete malicious-domain control, and an IGNORE action intentionally produces no response and a client timeout. No current deployment state or change approval follows from the source alone. Validate Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution, and treat examples or options as conditional inputs rather than defaults. ## Applicability questions - For source statement 1 at Article introduction, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Section ‘Query filter criteria’, which observable configuration, record, or test can confirm applicability here? - What inventory proves which parts of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles are in and out of scope? - Which condition in Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution must be healthy before evidence is trustworthy? - What result would disprove the working assumption and return the issue to the owner? ## 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. For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence. ## Verification and evidence Build a reproducible chain from Article introduction; Section ‘Query filter criteria’ to the observed environment. Useful domain evidence includes PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands; label every item with scope, timestamp, collector, and stable identifier. Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes. ## Official references - [Use DNS Policy for Applying Filters on DNS Queries](https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/apply-filters-on-dns-queries) — Microsoft ## Primary reference - Name: Use DNS Policy for Applying Filters on DNS Queries - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/apply-filters-on-dns-queries - Source publication date: 2021-07-29 ## Citation and use Preferred citation: “Filter Windows DNS queries only with explicit match and timeout tests,” DSE Security, https://update.dsesecurity.com/updates/filter-windows-dns-queries-only-with-explicit-match-and-timeout-tests/ 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.