DHCP (Dynamic Host Configuration Protocol) automatically provides network configuration to clients. Instead of manually configuring every computer, a DHCP server can assign an IP address and provide other network settings.

When a client joins a network, it can use the DHCP process commonly remembered as DORA:

Common DHCP options

DNS translates names into IP addresses, but in an Active Directory environment it does more than resolve ordinary hostnames. It also publishes information about services available in the domain.

Domain Controllers register DNS records that advertise services such as LDAP and Kerberos. These records allow clients to discover which servers provide the services they need.

In short, an SRV record helps the client discover which server provides a service. The client can then resolve that server’s hostname to an IP address.

A commonly used SRV record for locating Domain Controllers is:

_ldap._tcp.dc._msdcs.example.com

Replace example.com with your own Active Directory DNS domain name.

Breaking down the record

The SRV response contains information such as:

• Priority: Lower values are preferred.
• Weight: Helps distribute selection among records with the same priority.
• Port: The port on which the advertised service is available. LDAP commonly uses TCP port 389.
• Target: The hostname of the server providing the service.

1. The client gets its network configuration. DHCP provides an IP address, subnet mask, default gateway and DNS server information. A statically configured client can have these settings configured manually.
2. The client contacts its configured DNS server. The Windows DC Locator process uses the Netlogon service to help find a suitable Domain Controller.
3. The client queries for SRV records. For example, it can query _ldap._tcp.dc._msdcs.example.com.
4. DNS returns the service information. The response identifies Domain Controller hostnames and includes service details such as priority, weight and port.
5. The client resolves the Domain Controller hostname. It uses DNS address records, such as A or AAAA records, to obtain an IP address.
6. The client checks Domain Controller availability. DC Locator uses an LDAP UDP-based discovery check to verify that a candidate DC is available.
7. The client selects and remembers a suitable DC. The Netlogon service caches discovered Domain Controller information to help with later requests.

In larger environments, an organization may have multiple physical locations connected by WAN links. Active Directory Sites represent the network topology and help clients locate suitable Domain Controllers.

Administrators associate IP subnets with Active Directory Sites. When a client locates a Domain Controller, the DC Locator process can use site-specific DNS records to find a DC in the client’s own site.

A site-specific LDAP SRV record can look like this:

_ldap._tcp.Mumbai._sites.dc._msdcs.example.com

Here, Mumbai is an example Active Directory site name. Your actual site name depends on how the Active Directory environment is configured.

Check the client’s network configuration

ipconfig /all

Displays the client’s IP configuration, including its DNS servers, default gateway and DNS suffix information.

Check which DNS servers are configured

Get-DnsClientServerAddress

PowerShell displays the configured DNS server addresses for the network interfaces.

Query the Domain Controller SRV records

Resolve-DnsName -Type SRV -Name "_ldap._tcp.dc._msdcs.example.com"

Returns the SRV records registered for Domain Controllers in the specified domain.

Use NSLOOKUP as an alternative

nslookup -type=SRV _ldap._tcp.dc._msdcs.example.com

This performs an SRV lookup using the Windows DNS diagnostic utility.

Ask Windows to locate a Domain Controller

nltest /dsgetdc:example.com

Displays information about a Domain Controller located for the specified domain, including its name and other details.

Check the domain secure channel

nltest /sc_verify:example.com

Checks the secure channel between the computer and the specified domain.

Refresh the DHCP lease

ipconfig /release
ipconfig /renew

Releases and requests an IPv4 DHCP lease. Use this when you need to renew DHCP-provided network configuration.

If a domain-joined computer cannot locate a Domain Controller, start with the basics. DNS configuration is one of the first things to investigate.

1. Check the IP configuration. Run ipconfig /all and verify the IP address, subnet mask, default gateway and DNS server addresses.
2. Check the DNS server. Make sure the client is using a DNS server that can resolve the Active Directory DNS zone. In a typical AD environment, this is an internal DNS server, often hosted on a Domain Controller.
3. Test name resolution. Try resolving the domain name and a known Domain Controller hostname.
4. Check the SRV records. Query _ldap._tcp.dc._msdcs.example.com and confirm that the expected records are returned.
5. Check Domain Controller discovery. Run nltest /dsgetdc:example.com to see whether Windows can locate a DC.
6. Check the Domain Controller itself. Verify that DNS and Netlogon are functioning and that the DC has registered the expected records.

Think of it this way:

Both services are important in a typical Active Directory network. DHCP helps configure the client, and DNS helps the client find the services it needs.

1. Windows clients normally use DNS-based discovery to locate Domain Controllers.
2. DHCP provides network configuration, including DNS server addresses.
3. DHCP does not normally tell a client which Domain Controller to use.
4. Active Directory Domain Controllers register service information in DNS.
5. SRV records advertise services such as LDAP and Kerberos.
6. _ldap._tcp.dc._msdcs.example.com is an important DC locator record.
7. The SRV response includes a target hostname, port, priority and weight.
8. The client resolves the target hostname to an IP address and checks DC availability.
9. Active Directory Sites help clients locate suitable Domain Controllers.
10. Resolve-DnsName and nltest are useful troubleshooting tools.

• Locating Active Directory Domain Controllers — Microsoft’s explanation of the DC Locator process, DNS discovery and site selection.
• Verify that SRV DNS records have been created — How to verify Active Directory SRV records using DNS Manager and NSLOOKUP.
• DHCP scopes in Windows Server — DHCP scopes and common configuration options.
• Install and configure DHCP Server — Configuring DHCP scopes and common client options.
• Resolve-DnsName PowerShell reference — PowerShell DNS query command documentation.

This article is an independently written learning guide about DHCP, DNS and Active Directory Domain Controller discovery. ChatGPT was used as an AI-assisted drafting and formatting tool. Technical explanations were checked against the Microsoft documentation linked above.

Examples use example.com as a placeholder domain. Replace it with the DNS name of your own Active Directory domain when testing commands. Always validate configuration changes in a suitable test environment before applying them in production.