A home printer works for weeks, then one morning the computer cannot find it. A camera that streamed reliably suddenly needs setting up again. Often the cause is an address that changed underneath the device, because most home gadgets are handed a new number by the router whenever it suits the network. Knowing the difference between an address that moves and one that stays fixed, and knowing the safe way to pin one down, saves a great deal of guesswork. This guide covers how addresses are assigned, when a fixed one is worth it, and how to set it without causing conflicts.
How addresses are handed out
Nearly every home network hands out addresses automatically through a system called DHCP, which runs on the router. When a device joins, whether over the latest Wi-Fi standard or a plain Ethernet cable, it requests an address, and the router hands one out from its pool for a set period known as a lease. The standards those devices use to connect are the sort the guide on Wi-Fi generations compared lays out.
Before the lease ends the device usually renews and keeps the same number, which is why addresses often appear stable for a while. But if a device is switched off long enough for the lease to expire, or the router restarts, the pool may hand that address to something else and give the returning device a different one. This automatic churn is normal and, for phones and laptops, entirely harmless.
Static addresses and reservations
A static address is one that does not come from the pool at all. Instead the device is told to always use a specific number, and it keeps that number regardless of leases or reboots. There are two quite different ways to achieve a fixed address, and confusing them causes most of the trouble people run into.
The first is a manual static address set on the device itself, typing the number into the phone, computer or camera. The second is a DHCP reservation, set on the router, which ties a chosen address to a device’s hardware identifier so the router always loans it the same one. A reservation looks static from the device’s point of view, yet the router stays in charge of it. The table below compares the three arrangements on the factors that matter in practice.
| Factor | Dynamic (pool) | DHCP reservation | Manual static |
|---|---|---|---|
| Set where | Router, automatic | Router, per device | On the device itself |
| Address stability | May change | Always the same | Always the same |
| Conflict risk | Very low | Very low | Higher if chosen carelessly |
| Survives router changes | Yes | Usually | Can break |
| Best for | Phones, laptops | Printers, servers, cameras | Rare, specific cases |
When a fixed address helps
Most devices are happier left on automatic, but a few benefit from staying put. Anything you reach by its address rather than a name is a candidate: a network printer, a NAS holding backups, a home server, or a camera you view from your phone. Port forwarding, which sends incoming connections to one device, also needs that device to keep a steady address, otherwise the rule points at the wrong machine after a reshuffle.
Traffic rules are another case. Prioritising a games console or a work laptop so it gets bandwidth first depends on the router recognising the same device each time, and that is far simpler when its address never moves, the kind of prioritising the guide on how a router ranks traffic explains. For ordinary browsing devices, though, a fixed address adds management effort for no real gain.
The risks of doing it by hand
Manual static addresses cause more problems than reservations because the router does not know they exist. If you type in an address that still sits inside the DHCP pool, the router may later loan the same number to another device, and the two then fight over it. That address conflict shows up as a connection that works intermittently or not at all, and it can be maddening to trace.
Another hazard is getting the supporting details wrong. A manual address also needs the correct subnet mask, gateway and DNS entries, and a small mistake in any of them leaves the device online in name only. A device that cannot reach anything after a manual change has an addressing fault, not a signal problem, which is separate from the channel settings the guide on Wi-Fi channels and width covers. Reservations avoid all of this by letting the router keep track for you.
Setting one safely
For almost everyone, the safe route is a DHCP reservation rather than a manual address. Open the router’s admin page, find the DHCP or connected-devices section, pick the device from the list, and reserve its current address. Because the router does the work, the address stays clear of the pool and the supporting details are filled in automatically.
If you must set an address manually, choose one outside the DHCP pool’s range to avoid clashes, and copy the subnet mask, gateway and DNS from a working device. After assigning it, a short connection test confirms nothing else is answering to the same address, the sort of measurement the guide on latency, jitter and loss describes. Note the address somewhere, because a fixed number you have forgotten about can puzzle you months later when you rearrange the network.
Choosing the right approach
The distinction that matters is not really static against dynamic, but who keeps track of the address. Leave the everyday devices on the automatic pool, where changes cost nothing and conflicts are rare. For the handful of machines you reach directly or forward ports to, give them a reservation so the address holds without you having to manage it by hand.
Manual static addressing has its place, mainly on equipment that must work before any DHCP server is running, but it is the option most likely to bite. Reaching for a reservation first keeps the router aware of every address on the network, which is exactly what prevents the silent conflicts that make addressing feel harder than it is. Set the few devices that need it, note what you did, and the rest can look after themselves.
Frequently asked questions
Do I need a static IP?
Most people do not. Phones, laptops and tablets work best on automatic addresses that the router manages for them. A fixed address helps only for devices you reach directly, such as a printer, a NAS, a home server or a camera, or when you forward ports to one machine. Even then, a DHCP reservation usually does the job more safely than a truly manual static address.
What is a DHCP reservation?
A DHCP reservation is an instruction on the router that always gives a particular device the same address. The router matches the device by its hardware identifier and loans it a chosen number every time it connects. From the device’s side it looks like a fixed address, but the router still manages it, so the address stays out of the general pool and conflicts are avoided.
Why does my device’s IP keep changing?
Because the router loans addresses for a limited period called a lease. If a device is off long enough for its lease to expire, or the router reboots, it can receive a different address from the pool next time. This is normal for automatic addressing and harmless for browsing. If a device needs a steady number, set a reservation for it on the router.
