Active Directory cannot function without healthy DNS, and clients get their addressing from DHCP. Together they're the plumbing every Windows network relies on.
DNS — name resolution
How DNS Resolves a Name
From typing a web address to receiving an IP — step by step.
Tap or hover a part to learn more.
Already known?
The browser and OS check their local DNS caches first. If the name is cached and not expired, the IP is returned instantly.
Check your understanding
1. What is checked first when resolving a name?
2. Which server returns the actual IP for a domain?
Keep learning
DNS turns names into IP addresses. In a domain, clients locate Domain Controllers via SRV records in DNS — which is why "AD is broken" so often turns out to be a DNS problem.
DHCP — automatic addressing
How DHCP Assigns an Address (DORA)
Discover, Offer, Request, Acknowledge — how a device gets its IP.
Tap or hover a part to learn more.
Client shouts.
A client with no IP broadcasts a DHCP Discover to find any DHCP server on the network.
Check your understanding
1. What is the correct DHCP order?
2. What does a 169.254.x.x address indicate?
Keep learning
DHCP hands clients an IP address, subnet mask, gateway and DNS servers automatically via the DORA exchange (Discover, Offer, Request, Acknowledge). Pointing clients at the wrong DNS server is a classic cause of domain issues.
Why it matters
DNS and DHCP are shared with our Networking Fundamentals path and are core Network+ and support topics. In a Windows domain, always suspect DNS first.
