No, the Windows DNS Client service does not receive or hand out a DHCP address. DHCP is handled by the network adapter, the Windows DHCP Client component, and the router or DHCP server; DNS Client is for name resolution, not lease assignment. If Windows is missing a normal IP address, start with the link, the adapter, and the DHCP lease, not DNS settings.
Does the DNS Client service hand out DHCP addresses?
No. DNS Client resolves names, such as a host name to an IP address; it does not assign the IP address itself. When DHCP is working, the adapter talks to the DHCP server and Windows records the lease through the DHCP Client side of the stack.
That matters because people often chase DNS first when the real failure happened earlier. If the machine never got a lease, DNS may look wrong simply because Windows never had a valid address to begin with.
What it looks like when Windows does not get a DHCP lease
The usual sign is that Windows has no usable IPv4 address or falls back to 169.254.x.x. That self-assigned address means Windows could not get a lease from DHCP, so it gave itself an automatic private address instead.
You may also see limited connectivity, no default gateway, or a network icon that says it is connected even though nothing actually reaches the network. A weak Wi‑Fi link, a bad cable, or a disabled adapter can look like a DHCP problem before the router has even had a chance to answer.
Check the adapter, link status, and lease details first
Start with the physical and adapter checks before you change settings. Make sure the Ethernet cable is seated, the Wi‑Fi connection is really on the right network, and the adapter is enabled. A link problem can stop DHCP before Windows ever gets to the request/response part.
Then open ipconfig /all and compare a few fields. IPv4 Address tells you what Windows actually has; Default Gateway shows whether it has a route off the local network; DHCP Enabled should be Yes; and DHCP Server should point to the server that handed out the lease. If you see 169.254.x.x, no gateway, or no DHCP server listed, DHCP did not complete.
ipconfig /allIf one PC fails while other devices on the same network get normal addresses, the problem is more likely local to that PC, that adapter, or that port. If every device on that segment fails, the router, switch, access point, or DHCP server becomes the stronger suspect.
Fixes in the safest order
- Reconnect the link.
Unplug and replug the Ethernet cable, or disconnect and reconnect Wi‑Fi. This is the lowest-risk check and it often clears a stale link or association problem. If the machine gets a normal address right after reconnecting, you can stop there.
- Renew the lease.
Ask Windows for a fresh DHCP lease before you change anything deeper.
ipconfig /release
ipconfig /renewIf ipconfig /renew returns a valid IP address, gateway, and DNS servers, DHCP is working again. If it fails, the exact message varies, but the result tells you something useful: either Windows still cannot reach the DHCP server, or the adapter is not in a healthy state.
- Restart the adapter.
Disable and re-enable the network adapter in Settings or Control Panel, or from Device Manager if needed. This helps when the adapter is stuck, misbound, or carrying a bad state after sleep, a dock change, or a driver hiccup. If only one adapter fails while another works, focus on the bad adapter instead of the whole PC.
- Reset the network stack only if the simpler steps fail.
netsh winsock reset
netsh int ip resetAfter that, restart Windows. If the PC still cannot get a DHCP lease, the problem is less likely to be a simple Windows stack glitch and more likely to be the adapter, the cabling or Wi‑Fi link, or the network side.
When to suspect the router, switch, or ISP side
Look beyond Windows when multiple devices fail at the same time, or when the DHCP server address in ipconfig /all points to something that is down or unreachable. That is the point where the router, switch, access point, or ISP-side equipment becomes more likely than the PC itself.
A bad switch port, a flaky Ethernet cable, a weak access point connection, or a DHCP server that has run out of leases can all produce the same symptom from the user’s side. If other devices on the same network still get addresses but this Windows PC does not, the fault is usually local to that PC or adapter. If nothing on that segment gets a lease, work the problem outward from the router or DHCP server.
A healthy result after the fix looks like this: Windows shows a normal IPv4 address, a default gateway, and one or more DNS servers; DHCP Enabled is still Yes; and ipconfig /renew completes without error. That means DHCP succeeded and DNS can now do its job on top of a working lease.
Frequently Asked Questions
Does the DNS Client service get a DHCP address?
No. DNS Client resolves names, while DHCP address assignment comes from the network adapter, the DHCP Client side of Windows, and the DHCP server or router. If you see `169.254.x.x` or no gateway, DHCP failed before DNS mattered.
How do I tell a DHCP problem from a DNS problem?
Use `ipconfig /all`. A valid IP address and gateway with broken name resolution points more toward DNS. A `169.254.x.x` address, no default gateway, or no DHCP server listed points to DHCP or a link problem first.