| Previous | Next |
| ERROR_PASSWORD_MUST_CHANGE | ERROR_ACCOUNT_LOCKED_OUT |
ERROR_DOMAIN_CONTROLLER_NOT_FOUND
No domain controller was found for the domain.
ERROR_DOMAIN_CONTROLLER_NOT_FOUND is Win32 error 1908 (0x774). Domain-controller discovery depends on the requested domain, DNS SRV records, site information, network reachability, Netlogon, flags such as writable or global-catalog requirements, and cached locator data. The error means the locator did not return a controller satisfying the request.
Why discovery returns no controller
- the client uses public or incorrect DNS servers that cannot resolve the Active Directory zone
- required SRV or host records are missing, stale, or filtered by split DNS
- firewall, VPN, routing, or time synchronization problems prevent communication with available controllers
- the requested site, writable-DC, KDC, or global-catalog criteria exclude all reachable servers
- Netlogon or DNS registration is unhealthy on domain controllers or the member computer
Discovery evidence to retain
Capture the requested DNS and NetBIOS domain names, locator flags, client site and subnet, DNS server list, SRV query results, selected protocol and ports, cached DC information, Netlogon events, network path, and whether forced rediscovery changes the result. Do not log domain credentials or Kerberos tickets. Include exact timestamps because DNS, VPN, and site state can change quickly.
Diagnostic sequence
Verify the client’s DNS configuration first and query the domain’s controller SRV records using the same resolver path as the application. Use DsGetDcName with the intended flags and compare cached lookup with DS_FORCE_REDISCOVERY. Confirm that returned controllers are reachable and that the client clock is within domain requirements.
Check subnet-to-site mapping, controller service health, DNS registration, replication, and firewall rules. If a broad lookup succeeds but a writable or global-catalog request fails, troubleshoot the missing capability rather than general connectivity. A hosts-file entry is not a substitute for correct DC locator records.
Recovery strategy
Correct DNS and routing, restore required controller services and records, or adjust an incorrect locator requirement. Flush or force rediscovery only after the underlying issue is fixed. For remote devices, ensure the domain path is established before components that require a controller start.
Applications should log their locator flags, tolerate temporary offline operation only when their security model allows it, and retry with bounded backoff. Administrators should monitor SRV registration and site coverage from client networks.
Difference from trust inconsistency
ERROR_DOMAIN_TRUST_INCONSISTENT means a reachable domain identity conflicts with stored trust data. Error 1908 occurs earlier: no suitable controller was discovered for the requested operation.
Example
A laptop connects to a third-party VPN that replaces corporate DNS with a public resolver. DsGetDcName returns 1908 because the AD SRV records are invisible. Restoring split-tunnel DNS for the domain makes a controller discoverable; resetting the computer account would not fix name resolution.
References
- Microsoft: System Error Codes (1700–3999)
- Microsoft: Win32 Error Codes in MS-ERREF
- Microsoft: DsGetDcName
- Microsoft: Verify DNS SRV records for a domain controller
Looking for a different code? Search another status or error code.