Plug a new laptop into a network and, within a second or two, it can reach the internet without anyone typing an address. That quiet handoff is DHCP doing its job. Understand how it hands out addresses, and a whole class of "I can't get online" tickets stops being a mystery.
This article maps to CompTIA A+ Core 1 (220-1201), Objective 2.6, which asks you to compare and contrast common network configuration concepts including DNS, DHCP, VLANs, and VPNs. The focus here is the DHCP half of that objective, and specifically the four terms in the title. The exam expects you to know what a scope, a lease, a reservation, and an exclusion each are, how they differ, and what breaks when they're set wrong. Those distinctions are also exactly what a technician configures on a real DHCP server or home router, so the exam knowledge and the job knowledge are the same knowledge.
DHCP hands out addresses so you don't have to
DHCP stands for Dynamic Host Configuration Protocol. Its purpose is to automatically assign IP addressing information to devices when they join a network, so nobody has to configure each machine by hand. On a network with dozens or hundreds of devices, manual addressing would be slow and error-prone, and two machines given the same address would create an IP conflict that knocks both offline.
DHCP doesn't just hand out an IP address. It typically delivers a full set of settings a device needs to communicate:
- The IP address itself
- The subnet mask, which defines the size of the local network
- The default gateway, the router the device uses to reach other networks
- One or more DNS server addresses, so the device can resolve names to addresses
Those extra settings are called DHCP options, and they matter because an address alone won't get a device online. A machine with an IP but no gateway can talk to its local neighbors but can't reach the internet. A machine with no DNS server can reach numeric addresses but can't resolve a name like a website. On the exam, remember that DHCP is responsible for the whole starter kit, not just the address.
DHCP servers come in several forms. On a home or small-office network, the DHCP server is usually built into the router. In a business, it often runs on a Windows Server or a dedicated network appliance. The role is the same regardless of where it lives: hold a pool of addresses and lease them out on request.
The DORA exchange is how a client gets its lease
When a device joins a network and needs addressing, it and the DHCP server run a four-step conversation. CompTIA and most networking courses teach it with the acronym DORA: Discover, Offer, Request, Acknowledge.
| Step | Sent by | Purpose |
|---|---|---|
| Discover | Client | Broadcasts "is there a DHCP server here?" |
| Offer | Server | Replies with an available address to use |
| Request | Client | Formally asks to take the offered address |
| Acknowledge | Server | Confirms the lease and finalizes settings |
The first message is a broadcast because the client has no address yet and doesn't know where the server is. It shouts to the whole local segment. The server that hears it responds with an offer drawn from its pool. The client then requests that specific address, and the server acknowledges, which locks in the lease.
You don't need to recite the packet details for the exam, but knowing the order helps you reason about failures. If a client never gets past Discover, either there's no DHCP server reachable, the server is out of addresses, or a network problem is blocking the broadcast. That single fact turns "the internet is down" into a much more specific troubleshooting path.
A scope defines the pool of addresses a server can give out
A scope is the range of IP addresses a DHCP server is configured to hand out, along with the settings that go with them. It's the master definition that everything else in this article sits inside. Without a scope, the server has nothing to lease.
A scope has a start address and an end address that bound the pool. For example, a small office might use a scope from 192.168.1.100 to 192.168.1.199. That gives the server one hundred addresses to assign. Along with the range, the scope carries the subnet mask, the default gateway, the DNS servers, and the lease duration that clients will receive. All of that is configured once at the scope level and applied to every device that gets an address from it.
Scope planning is a practical decision, not a formality. The pool has to be large enough for every device that might connect at the same time, including phones, laptops, printers, and guest devices. If a scope has 50 addresses and 60 devices try to connect, ten of them will fail to get a lease and fall off the network. A technician sizing a scope thinks about peak device count, not the average, because everyone plugging in on a busy Monday morning is what exhausts the pool.
It's also common to leave part of the subnet outside the scope on purpose. A network using 192.168.1.0/24 has 254 usable addresses, but the DHCP scope might only cover .100 through .199. The addresses below .100 are left for devices that need fixed, manually assigned addresses, such as the router, servers, and managed switches. Keeping those out of the dynamic pool prevents the server from ever handing a static device's address to something else.
In exam terms, when you see "scope," think "the range of addresses plus the settings a DHCP server offers." It's the container. Leases, reservations, and exclusions all describe how individual addresses within or around that container behave.
A lease is temporary, and the renewal timing matters
DHCP doesn't give a device an address forever. It grants a lease, which is permission to use an address for a set period of time. When the lease expires, the address can return to the pool. This design keeps addresses from being wasted on devices that have left the network.
The lease duration is set on the scope. On a home router it might default to 24 hours. On a corporate network it's often several days, sometimes eight days on Windows DHCP by default. The right length depends on how the network is used. A coffee shop with constant turnover of guest devices benefits from a short lease, maybe an hour, so addresses free up quickly for the next wave of customers. An office of stable desktops benefits from a longer lease, because those machines aren't going anywhere and there's no reason to churn the pool.
A device doesn't wait for the lease to fully expire before acting. It tries to renew partway through.