Overview
The DNS Server Settings monitoring test appears under the DNS Server indicator for a domain controller.
The DNS Server indicator itself is only shown for domain controllers where the DNS Server role is installed. ENow checks the role on each domain controller, and where it is present the indicator appears at the top level, to the right of AD Core. Where it is absent, no DNS Server indicator is shown for that server — this is expected and not a fault.
Monitoring Benefit
The DNS Server Settings test collects the DNS server configuration from the domain controller itself and reports it alongside the rest of that server's health. Because the domain controller is authoritative for AD-integrated zones, the settings read here are the settings Active Directory is actually using — not a cached or partial view seen from a resolver elsewhere on the network.
The test depends on the DNS Server service running. If the service is stopped, the settings cannot be read and the indicator reflects that rather than reporting stale configuration.
The collected settings are shown at the bottom of the monitoring results page for DNS Server Settings Status.
How do we verify the monitoring test results?
1. Read the same settings directly on the domain controller. ENow collects them with PowerShell, so the same call reproduces what the test sees:
Get-DnsServerSettingsCompare the output against what the monitoring results page shows. A difference between the two normally means the collection has not run since the setting changed.
2. Confirm the DNS Server service is running. This test reads configuration from the running service. If DNS.exe is stopped, the read fails.
Get-Service DNS3. Confirm the role is actually installed. If the DNS Server indicator is not appearing for a domain controller you expected it on, check the role rather than the test:
Get-WindowsFeature -Name DNSCommon warning or error results, and potential solutions
| Result | Potential solution |
| Settings cannot be collected | Confirm the DNS Server service is running on the domain controller. This test depends on it, and a stopped service prevents the read. |
| No DNS Server indicator for a domain controller | The DNS Server role is not installed on that server. The indicator is only presented where Get-WindowsFeature -Name DNS reports the role as installed. |
| Settings shown do not match the server | The collection has not run since the change. Compare against Get-DnsServerSettings on the server and allow a collection cycle to complete. |
| Collection fails on one domain controller only | Check the ENow Client on that server and its permissions to query the DNS server. WMI provider health (root\MicrosoftDNS) is worth checking where the DNS service is running but not answering. |
Related monitoring tests
These appear under the same DNS Server indicator:
- DNS Server Functionality — tests that the DNS server responds on each of its listening addresses.
- Forwarders Functionality — tests the configured forwarders.
- Root Hints Functionality — tests the root hints.
- Domain Records, Forest Records and Host Name Records.
Alerts for these tests are delivered under the DNS Server workload for domain controllers.
Comments
0 comments
Please sign in to leave a comment.