DHCP Explained: How Your Devices Get Their IP Addresses

Every device on your business network — every laptop, desktop, printer, phone, and server — needs an IP address to communicate. Without an IP address, a device simply cannot participate in the network. It cannot access the internet, connect to shared drives, print documents, or send emails. Yet despite this fundamental importance, most business owners and many office workers have never considered how their devices actually obtain these addresses. The answer, in the vast majority of cases, is a protocol called DHCP.

Dynamic Host Configuration Protocol, universally known as DHCP, is one of those invisible technologies that works silently in the background of every business network across the United Kingdom. When it is working correctly, nobody notices it. When it fails, everything stops. Understanding how DHCP works, why it matters, and how to manage it properly is essential knowledge for anyone responsible for a business network.

This guide explains DHCP in plain, practical terms — what it does, how it works step by step, why it is configured the way it is, and what can go wrong when it is misconfigured or fails.

What Is an IP Address and Why Does Every Device Need One?

An IP address is a unique numerical identifier assigned to every device on a network, much like a postal address identifies a specific building on a street. Just as the Royal Mail needs a precise address to deliver a letter, network traffic needs a precise IP address to reach the correct device. Without an IP address, data packets have no destination, and the device is effectively invisible on the network.

In most business networks, IP addresses follow the IPv4 format — four numbers separated by dots, such as 192.168.1.45. Each number ranges from 0 to 255, giving the system its familiar appearance. Private networks (those not directly exposed to the internet) typically use address ranges defined by international standards: 10.0.0.0 to 10.255.255.255, 172.16.0.0 to 172.31.255.255, or 192.168.0.0 to 192.168.255.255. The 192.168 range is by far the most common in small and medium-sized business networks in the UK.

Static vs Dynamic IP Addresses

There are two fundamental ways a device can obtain an IP address: statically or dynamically. A static IP address is manually configured on the device itself — someone physically types in the IP address, subnet mask, default gateway, and DNS server addresses. A dynamic IP address is automatically assigned by a DHCP server when the device connects to the network.

For most business devices — laptops, desktops, phones, and tablets — dynamic addressing via DHCP is the standard approach. Static addresses are typically reserved for infrastructure devices such as servers, printers, network switches, and access points, where a fixed, predictable address is important for management and accessibility.

How DHCP Works: The DORA Process

The DHCP process follows a precise four-step sequence that network engineers refer to as DORA — Discover, Offer, Request, Acknowledge. This elegant handshake happens every time a device joins your network, typically completing in milliseconds. Understanding each step helps demystify what happens when you plug in a network cable or connect to the office Wi-Fi.

Step 1: Discover

When a device first connects to the network, it has no IP address and no knowledge of the network's configuration. It sends a DHCP Discover message — essentially a broadcast shout across the entire local network saying "Is there a DHCP server out there? I need an IP address." Because the device does not yet have an IP address, this message is sent from the source address 0.0.0.0 to the broadcast address 255.255.255.255, ensuring every device on the local network segment receives it.

Step 2: Offer

The DHCP server receives the Discover message and responds with a DHCP Offer. This offer includes a proposed IP address from the server's available pool, along with configuration details such as the subnet mask, default gateway (the router address), DNS server addresses, and the lease duration. If multiple DHCP servers exist on the network, each may send an offer, but the client typically accepts the first one it receives.

Step 3: Request

The device receives the offer and sends a DHCP Request message back to the server, formally requesting the offered IP address. This message is also broadcast, which serves an important purpose when multiple DHCP servers exist — it informs all servers which offer was accepted, allowing the others to withdraw their offers and return the proposed addresses to their available pools.

Step 4: Acknowledge

The DHCP server confirms the assignment by sending a DHCP Acknowledge (ACK) message. The device now has a valid IP address and all the network configuration it needs to communicate. The entire DORA process typically takes less than a second, and the user is completely unaware it has happened.

DHCP Lease Duration and Renewal

When a DHCP server assigns an IP address, it does so for a specific period called a lease. Think of it like renting a parking space — the device has the right to use that IP address for the lease duration, after which it must either renew the lease or give up the address. This leasing mechanism ensures that IP addresses are efficiently recycled when devices leave the network.

Typical lease durations in business environments range from 4 to 24 hours. A shorter lease means addresses are reclaimed more quickly when devices disconnect, which is useful in environments with many transient devices such as guest Wi-Fi networks. A longer lease reduces the amount of DHCP traffic on the network and ensures devices maintain consistent addresses for longer periods, which can simplify troubleshooting and logging.

Devices do not wait until the lease expires to renew. At the 50% mark of the lease duration, the device automatically sends a renewal request to the DHCP server. If the server is available, it extends the lease, and the device continues with the same IP address. If the renewal fails (perhaps the server is temporarily unreachable), the device tries again at the 87.5% mark. Only if both renewal attempts fail does the device release the address and go through the full DORA process again.

DHCP Reservations: The Best of Both Worlds

DHCP reservations combine the convenience of automatic addressing with the predictability of static IP addresses. A reservation tells the DHCP server to always assign a specific IP address to a specific device, identified by its MAC address (a unique hardware identifier burned into every network interface). The device still uses the DHCP process to obtain its address, but the server always offers the same one.

This is the recommended approach for devices that need a consistent IP address — printers, servers, network-attached storage, VoIP phones, and other infrastructure devices. Using DHCP reservations rather than true static addresses means all IP address management remains centralised on the DHCP server, making it far easier to track, audit, and modify the network's addressing scheme.

Common DHCP Problems and How to Resolve Them

When DHCP fails, the symptoms are usually immediate and obvious: devices cannot connect to the network, users see "no internet" warnings, and productivity grinds to a halt. Understanding the most common DHCP failures helps you diagnose and resolve issues quickly.

DHCP Scope Exhaustion

If the DHCP server runs out of available IP addresses — because the pool is too small for the number of devices, or because leases are too long — new devices will be unable to obtain an address. The solution is either to expand the DHCP scope (add more addresses to the pool), reduce the lease duration so addresses are reclaimed faster, or identify and remove unused reservations that are consuming addresses unnecessarily.

Rogue DHCP Servers

A rogue DHCP server is an unauthorised device on the network that responds to DHCP Discover messages with incorrect configuration. This can happen when someone connects a personal router to the office network, or when a misconfigured device starts advertising DHCP services. The result is devices receiving wrong IP addresses, wrong gateway addresses, or wrong DNS servers — causing intermittent connectivity failures that can be extremely difficult to diagnose without proper network monitoring tools.

DHCP Best Practices for Business Networks

Proper DHCP configuration is a hallmark of a well-managed network. For UK businesses, the following best practices ensure reliable and secure IP address management across the organisation.

Always document your DHCP configuration, including the scope range, exclusions, reservations, and lease durations. Implement DHCP failover or redundancy so that a single server failure does not take down the entire network's addressing. Use DHCP reservations for all infrastructure devices rather than static assignments. Separate your DHCP scopes by VLAN to maintain logical network segmentation — for example, separate scopes for the corporate network, guest Wi-Fi, VoIP phones, and IoT devices.

Monitor your DHCP utilisation regularly. If your scope is consistently more than 80% utilised, it is time to plan for expansion before you experience scope exhaustion during peak periods. Enable DHCP snooping on your network switches to prevent rogue DHCP servers from distributing incorrect configuration to your devices.