How to diagnose a Windows DNS server with PowerShell. Learning PowerShell commands for Windows DNS lets your MSP automate tasks and troubleshoot issues faster, with less disruption, and better protection against DNS attacks. This guide will cover how to run targeted diagnostics, establish a baseline, and more using PowerShell commands and RMM tools. Before we begin, be sure to subscribe to NinjaOne's IT Video Hub and our YouTube channel for more tech content like this. Method 1: Triage the endpoint path first. Before troubleshooting DNS on the server side, rule out any client-side misconfigurations first. Complete the following steps before proceeding: Confirm that the client's network adapter can connect to the gateway and DNS servers. Then check that DNS record types match their correct IP addresses. For example, an AAAA record should point to an IPv6 address. Finally, review the DNS cache for any signs of trouble, such as incorrect query paths or unusually low TTL values. Method 2: Capture a DNS diagnostics baseline. Before making any changes, capture a snapshot of your current DNS server settings. This gives you a reliable reference point for tracing issues, and rolling back to a working state if needed. To do this: Press Win + R, type PowerShell, then press Ctrl + Shift + Enter to open it as an administrator. Check that the DNS server module is installed by running: Get-Module -ListAvailable -Name DnsServer If it's missing, install it with Install-WindowsFeature -Name RSAT-DNS-Server Export your DNS diagnostics settings as a CSV file by running: Or as a JSON file, by running: Check DNS event tracking and save the output: Save all exported files in your change management folder for easy access. Method 3: Enable targeted diagnostics. Only enable the diagnostics you actually need to avoid excessive logging and reduce the impact on production systems. This keeps logs manageable, reduces strain on your production environment, and makes it easier to pinpoint the root cause of DNS failures. To do this method, open PowerShell. Determine which DNS layer is causing problems. It could be a query resolution, zone transfer, dynamic update, or forwarding issue. To view your currently enabled diagnostic flags, run: Get-DnsServerDiagnostics Enable only the flags you need (for example, Query and Send): For deeper insights, temporarily enable debug logging: Replace with the maximum size per log file, for instance, 10. Replace with the maximum total size allowed across all log files, for instance, 50. Then, document your changes: To save updated diagnostics settings, run: Then, document the debug log status by running: PowerShell scripts help your team deploy and document DNS troubleshooting quickly. Paired with a structured playbook and a reliable RMM tool, they help MSPs build client trust, support continuous monitoring, and improve DNS troubleshooting over time. For more information, check out our official blog post on diagnosing a Windows DNS server with PowerShell, linked in the description below.