Windows Server / Active Directory & Group Policy
Diagnose missing domain-controller SRV records
A member server may reach a controller's address but fail to locate domain services. Query the records the locator process depends on.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Resolve-DnsName -Name '_ldap._tcp.dc._msdcs.corp.example.com' -Type SRVRead the result
In PowerShell, replace the sample domain with the real AD DNS name. SRV targets, priorities and ports describe advertised discovery endpoints.
Resolve and verify
Confirm each intended target resolves and is reachable through the member's approved DNS path. Repair missing registration or zone replication through the AD DNS owner.
Before changing production
Do not create guessed records or publish internal domain queries to unrelated external DNS services.