Why Does Your IP Address Assign Itself? ── DHCP Explained Through a “Move-In Process” (DORA, Leases, Pool Exhaustion, and the Truth About 169.254)

You type in the Wi-Fi password at a coffee shop. That’s it ── the web just works. You never entered an address (an IP address), and you don’t even know what your device’s IP address is. If communication still starts, it’s because someone, somewhere, must be assigning your device an address. That “someone” is today’s protagonist: DHCP. If any of these sound familiar, read on.

• You’d never thought about why joining a Wi-Fi network is all it takes to get online
• You don’t know what “Obtain an IP address automatically” in the settings screen actually means
• IT at work told you to “set it to DHCP” or “use automatic” ── and you complied without knowing what you agreed to
• Your device once showed a mysterious 169.254.x.x address and refused to reach the internet

DHCP (Dynamic Host Configuration Protocol) is, in one sentence, the building manager that automatically lends an address, on a fixed-term lease, to any device that joins the network. But that one sentence doesn’t explain why it’s a loan, what exactly is being handed out, or what happens when the lending fails.

This article stays completely out of OS and router setup instructions and walks through:

• The manual era ── why automation became inevitable (§1)
• The four-step move-in process ── DORA (§2)
• Leases ── why it’s a loan, and why it expires (§3)
• It hands out more than an address ── the four-item kit (§4)
• The days it goes wrong ── 169.254, pool exhaustion, and rogue managers (§5)

── taking the shortest path through the logic, and nothing else. By the end, that instruction from IT will make sense: it was an application to “leave address management to the building manager.”

Your question	Section
Who assigns addresses, and how?	§1 / §2
What does “obtain automatically” actually do?	§2
Why is it a loan with an expiry date?	§3
What else gets handed out besides the IP address?	§4
What is 169.254.x.x? Why am I offline?	§5

1. The manual era ── why automation became inevitable

1-1. Communication takes more than an address ── the four-item kit

For a device to start communicating on a network, at minimum four settings must be in place: its own address (the IP address), the boundaries of its own neighborhood (the subnet mask), the location of the town’s exit (the default gateway), and the location of the phone-book service (the DNS server). We’ll look at what each one means in §4 ── for now, the important part is simply that there are four of them.

Once upon a time, administrators typed this four-item kit into every single device, by hand.

1-2. How manual collapsed ── duplicates, ledgers, and devices that move

The manual era ── admins typing the four-item kit into every device

 Per PC:   IP address     192.168.1.23   ← cross-checked against a ledger, typed by hand
           Subnet mask    255.255.255.0
           Gateway        192.168.1.1
           DNS            192.168.1.1

 How it collapses:
  - one missed ledger update → the same address on 2 devices (duplicate = both misbehave)
  - 10 devices → 100 → 1000…  (ledger upkeep becomes a full-time job)
  - laptops and phones arrive → re-type everything for a device that visits for one day?

The manual approach collapsed for three reasons. One: humans make mistakes. Forget a single ledger update and the same address gets assigned to two devices ── both start misbehaving. Two: as device counts grow, maintaining the ledger becomes a job in itself. And three was the knockout blow: the age of devices that move. Laptops and phones hop from this network today to that one tomorrow. An operation where an administrator types settings in at every arrival simply cannot work, as a matter of principle.

1-3. The change of approach ── “lend on arrival, on the spot”

So the approach flipped. Instead of devices carrying fixed addresses, a building manager lends an available address, on the spot, to any device that joins the network. The agreed rules for that manager’s job are DHCP. The device-side setting collapses to a single choice ── “I’ll get my address from the manager” ── and the hand-typing of the four-item kit and the ledger upkeep all move to the manager’s side.

2. The four-step move-in process ── DORA

2-1. How do you ask for an address when you don’t have one?

Here’s where it gets interesting. A device that hasn’t received an address yet has no address. No address means it can’t fill in a sender or a recipient ── ordinary communication is impossible. So how do you send the request for an address, with no address?

The answer is broadcast (a transmission that reaches everyone present). Instead of addressing anyone in particular, the device shouts: “Everyone on this network, please listen!” It’s a building-wide PA announcement ── something you can do even with no address. The move-in process starts with this shout.

2-2. DORA ── shout, offer, apply, sign

The lending always runs through the same four steps, known by their initials as DORA.

1. 1DiscoverDevice: “Can anyone lend me an address?!” ── a device with no address shouts to everyone on the network.
2. 2OfferManager: “There’s a vacancy. How about 192.168.1.23?” ── picks an available address from the ledger and offers it.
3. 3RequestDevice: “I’ll take that one, please!” ── also shouted to everyone (see the pitfall below for why).
4. 4AckManager: “Deal. Your lease runs for 24 hours.” ── records it in the ledger and states the lease term.

In the brief moment between typing the Wi-Fi password and the first page loading, these four exchanges have already finished. As long as “obtain automatically” is selected, your device quietly runs this move-in process on every network it ever joins.

3. Leases ── why it’s a loan, and why it expires

3-1. Give addresses away forever, and you can never get them back

Why does the manager lend addresses instead of giving them away? Because permanent handouts mean devices that left keep holding their addresses. Think of a coffee shop’s Wi-Fi. If every customer’s device kept its address forever, the vacancies (the address pool ── the stock of lendable addresses) would run out in no time. And the customer may never come back.

So every loan carries an expiry date. This is the lease (a fixed-term lending contract). If the term runs out with no extension, the address returns to stock and gets lent to the next device.

3-2. Renewal ── “extend me, please” at the halfway mark

“If there’s an expiry date, won’t it cut me off mid-use?” ── just like an apartment lease, there’s a renewal. Around the halfway point of the lease term, the device asks the manager: “the address I’m using ── extend it, please.” A device in active use gets renewed onto the same address essentially every time, which is why you never have to think about the expiry.

The manager's ledger and a lease's timeline

 Ledger (address pool):
  192.168.1.21  → on loan (phone A, expires 2:00 pm)
  192.168.1.22  → vacant
  192.168.1.23  → on loan (PC B, expires 6:30 pm)

 Life of a lease:
  signed ──────── halfway mark ─────────────── expiry
   │                │ "extend me, please"          │
   │                └→ approved → term extended    └→ no extension → back to stock

3-3. And that’s why “your IP address can change”

The consequence of this design is that dynamic IPs (addresses that can change) became the modern default. Power a device off long enough for its lease to lapse, and the move-in process on its return may hand it a different address. The “private IPs can change after a restart” we saw in §8 of the IP address article is exactly this: a lease expiring and a new contract being signed.

4. It hands out more than an address ── the four-item kit

4-1. The move-in process includes a welcome packet

As §1 showed, communication needs the four-item kit. During the DHCP move-in process, the other three items get handed out along with the address ── like the welcome packet you receive when moving into a building.

What’s handed out	Think of it as	Without it
IP address	your apartment’s address	you can’t participate in communication at all
Subnet mask	the line marking “this far is our neighborhood”	you can’t tell neighbors from out-of-towners
Default gateway (the router)	the town’s only exit	you can talk locally, but never reach the internet
DNS server	where the phone-book service lives	you can only dial raw addresses ── no names

4-2. The real reason “just connect and browse” works

“Join the Wi-Fi and the web just works” holds because all four items arrive in one single move-in process. You receive an address, learn your neighborhood’s boundaries, learn where the town’s exit is, and learn where the phone book is ── all settled, which is why typing a name into a browser is all you ever do. What’s inside the phone book is the DNS article; the address rewriting that happens beyond the town’s exit is the NAT article.

5. The days it goes wrong ── 169.254, pool exhaustion, and rogue managers

5-1. 169.254.x.x ── the placeholder address when the manager won’t answer

When the internet is down, a peek at the settings screen sometimes shows your IP address as an unfamiliar 169.254.x.x. That’s not an error code. It’s the placeholder address a device assigns itself when “I shouted, and no manager answered” ── a link-local address.

The fall to 169.254

 Device: "Can anyone lend me an address?!" (Discover)
   │
   ├─ answer received → move-in process (§2's DORA) → all good
   │
   └─ no answer (no matter how many shouts)
        └→ Device: "Fine ── I'll name myself a placeholder."
            → 169.254.x.x (link-local address)
               - only valid within the local network
               - knows no town exit (gateway) = cannot reach the internet

The placeholder works for talking within the local network, but since no move-in process happened, the device was never told the town’s exit or the phone book’s location. So: no internet. That’s why the correct reading of this number is “169.254 means the device isn’t broken ── DHCP is unreachable (the shout isn’t getting through, or the manager isn’t responding).”

5-2. Pool exhaustion ── zero vacancies, no new move-ins

The manager’s stock (the address pool) has a ceiling. As employee phones, meeting-room gear, and IoT gadgets keep piling up and vacancies hit zero, newly arriving devices can shout Discover all they want ── there’s no address to lend. Nothing is broken, yet “only the new devices can’t join the network.” The symptom and its causal chain are diagrammed in §5 of Why Is the Office Network Slow?.

5-3. Rogue managers ── when the welcome packet is a lie

One last risk worth knowing. As §2 showed, a device fundamentally trusts the first manager that answers. If a rogue DHCP server (a fake manager) on the same network answers first, the device receives a forged four-item kit ── and if “the town’s exit is here” and “the phone book is here” all point at an attacker’s equipment, your traffic gets routed and steered wholesale.

This is the DHCP version of the “on public Wi-Fi, strangers are inside the wall with you” problem from the firewall article. The countermeasures are ones you already know: on untrusted networks, wrap your traffic whole in a VPN envelope, and use HTTPS sites (contents encrypted). Even if a fake manager bends your route, what keeps you safe is making sure the contents still can’t be read.

Summary ── the four-line essence

1. DHCP is the building manager that lends arriving devices an address on a fixed-term lease. Manual configuration collapsed under duplicates, ledger upkeep, and devices that move ── automation was inevitable
2. Lending runs through DORA’s four steps (shout → offer → apply → sign). Broadcast ── communication that needs no address ── is the way in, and “obtain automatically” is precisely this move-in process
3. Because it’s a lease, addresses get reclaimed and reused ── and that’s why your IP can change. And it hands out not just the address but the full four-item kit: neighborhood boundary, town exit, and phone-book location
4. The signs of a bad day: 169.254.x.x (a placeholder ── you never spoke to the manager) and pool exhaustion (zero vacancies). Against rogue managers, the familiar defenses apply: VPN and HTTPS

The address itself is covered in What Is an IP Address?, the phone book that turns names into addresses in What Is DNS?, the address translator in What Is NAT?, and the slowness born of pool exhaustion in Why Is the Office Network Slow?. Assignment (DHCP), translation (NAT), and name resolution (DNS) ── the life of an address should now connect end to end.

FAQ

Q1. Automatic or manual (static) ── which should I use?

A. For ordinary devices, automatic (DHCP) ── full stop. It’s the default precisely because it structurally prevents manual duplication accidents (§1). Even for devices you want pinned to one address (printers, home servers), the standard move is a DHCP reservation (static assignment) written on the manager’s ledger rather than hand-configuring the device (§3’s Tip). For work machines, your company’s instruction wins ── if they say “use DHCP,” that’s the rule of that network.

Q2. I’m stuck on 169.254.x.x and can’t get online ── what’s happening?

A. Your device shouted “lend me an address” and got no answer from the manager (the DHCP server), so it named itself a placeholder (§5-1). The device isn’t broken ── the lending failed somewhere between it and the manager: cabling or Wi-Fi association, the router’s DHCP function, or the manager’s stock running dry. Reconnecting, or restarting the router so the move-in process runs again, is the first move that actually matches the mechanics.

Q3. Why does my IP address sometimes change after restarting the router?

A. Because it’s a lease (a fixed-term loan) (§3). If a restart or a long power-off lets the lease lapse, the move-in on return is a fresh contract, and a different vacant address may be lent out. The same structure applies to both your in-home private IP and the global IP your home borrows from the ISP (see also the IP address article’s FAQ).

Q4. I want the same device to always get the same IP address.

A. Use a DHCP reservation (static assignment) (§3’s Tip). It’s a named contract in the manager’s ledger ── “this device always gets this address” ── while the device itself stays on “obtain automatically” and simply receives the same address every time. Unlike typing a fixed value into the device, the ledger remains the single source of truth, so duplication accidents can’t happen. The setting lives in your router’s admin panel, but the steps vary by model, so this article stays at the structural explanation.

Q5. At the office, only new devices can’t connect ── is DHCP to blame?

A. The classic suspect for that symptom is pool exhaustion ── zero vacancies (§5-2). Devices already holding an address keep living there through renewals, while only newcomers get turned away ── that asymmetry (“existing devices fine, new ones can’t join”) is the tell. In modern offices where device counts only grow, it happens with zero hardware failures. The triage steps and causal chain are covered in Why Is the Office Network Slow?.