by Tommy N. Updated Apr 23, 2026
If you've ever set up a printer, game console, or smart home device only to find it stopped working after a router reboot, a reserved IP address is the fix you've been looking for. Reserving an IP address — also called a DHCP reservation or static DHCP lease — tells your router to always hand the same local address to a specific device, every single time it connects.
In this guide you'll learn exactly how to reserve an IP address on your router, why it's more reliable than manually configuring a static IP on the device itself, and how to avoid the common mistakes that leave devices unreachable. If you're not yet comfortable with concepts like how DHCP works or what an IP address actually is, a quick read of those guides first will make everything here click instantly.
Your router runs a service called DHCP (Dynamic Host Configuration Protocol) that automatically issues IP addresses to devices as they join your network. By default, these leases are temporary — a device may receive 192.168.1.105 today and 192.168.1.118 tomorrow after a reboot or a long period offline. That shifting address breaks any rule, forwarding entry, or shortcut that depended on the old one.
A DHCP reservation solves this by creating a permanent mapping between a device's MAC address and a specific IP address inside the router's lease table. The MAC address is a hardware identifier — a 12-character hexadecimal string like A4:C3:F0:85:2D:11 — that is baked into every network adapter at manufacture. Because the MAC address never changes, the router can recognise the device every time it asks for an address and hand back the same reserved IP without any configuration needed on the device itself.
This is fundamentally different from setting a static IP directly on a device's operating system. When you configure a static IP on a computer or phone, that device claims the address without asking the router, which means the router's DHCP pool could simultaneously hand that same address to another device and create a collision. A reservation keeps the DHCP server in charge: the device still requests an address normally, and the router fulfils that request with the reserved one. No collisions, no conflicts, and no manual network settings to maintain across multiple devices.
Reservations are particularly valuable for devices that need consistent network access: network-attached storage (NAS) drives, smart TVs, security cameras, printers, Raspberry Pi servers, and anything you've set up port forwarding rules for. The moment any of those devices change their IP, the rule stops working — a reserved address prevents that entirely.
The exact menu names vary between router brands (Asus, Netgear, TP-Link, Linksys, and so on), but the process follows the same five-step pattern on virtually every home router.
192.168.1.1 or 192.168.0.1. If you're unsure of your gateway, see our guide on how to find your router's IP address. Enter your admin username and password — if you haven't changed these, check router default passwords for your model.ipconfig /all in Command Prompt; on Android or iOS, check Settings → Wi-Fi → [Network name] → Advanced.Both approaches result in a device keeping the same IP address, but they work differently and each has trade-offs worth understanding before you commit to one for every device on your network.
| Method | Configured On | Conflict Risk | Best For |
|---|---|---|---|
| DHCP Reservation | Router | None (router controls pool) | Most home devices, printers, NAS |
| Static IP (device) | Device OS | Possible if not planned | Servers, VMs with known subnets |
| Dynamic DHCP (default) | Router | None, but address changes | Phones, laptops, guest devices |
| Static IP + Reservation | Both | None (belt-and-suspenders) | Critical infrastructure, NAS |
| Link-local (APIPA) | Device OS | None (169.254.x.x range) | Fallback only, no internet access |
Before entering a reserved address, log in to your router and note the start and end of your DHCP pool (often listed as Starting IP and Ending IP or DHCP Range). Pick your reserved addresses from outside that range — for example, if the pool is .100–.200, use .2 through .99 for reservations. This single step eliminates the most common cause of IP address conflicts on home networks.
Once you've set up a few reservations, maintenance is minimal — but there are some scenarios where things go wrong and a few habits that will save you headaches down the road. The most frequent issue is a device not picking up its reserved address after the reservation is saved. This almost always means the device's existing DHCP lease hasn't expired yet. Simply toggling the device's Wi-Fi or Ethernet off and on, or rebooting the device, forces a fresh DHCP request and the router will respond with the reserved address.
Another common problem arises when unexpected devices appear on your network with addresses that collide with your reserved ones. This typically happens when a guest device is manually configured with a static IP that lands inside your pool, or when a reservation was set up for an old device and the address was later reassigned manually elsewhere. Keeping a simple spreadsheet or text file that maps device names, MAC addresses, and reserved IPs takes about five minutes to set up and saves enormous time when diagnosing these conflicts later.
It is also worth periodically reviewing your reservation list — especially after replacing devices. When you get a new phone or printer, its MAC address changes and the old reservation becomes dead weight in the router's table. Clean up stale reservations to keep the list accurate and your available address space tidy.
Pro Tip: After setting up reservations for devices you've also configured port forwarding for, double-check that each forwarding rule targets the reserved address — not just whatever IP the device had when you first created the rule. Use our port checker tool to confirm the forwarded ports are reachable from outside your network after making changes.
A reserved IP address is configured on the router and delivered to the device via DHCP, so the device still obtains its address automatically — it just always gets the same one. A static IP is configured manually on the device itself, bypassing DHCP entirely. Reservations are generally safer for home networks because the router remains in control of address assignment, preventing conflicts. You can learn more about the underlying mechanism in our DHCP guide.
No — a DHCP reservation has no effect on network speed or Wi-Fi performance. The reservation only changes which IP address the router assigns during the handshake when a device joins the network; once the address is assigned, data flows exactly as it would with a dynamic lease. The entire reservation lookup adds microseconds to the connection process, which is completely imperceptible in practice.
The easiest method is to check your router's connected devices list — it shows the MAC address of every currently connected device alongside its hostname and IP. On Windows you can also run ipconfig /all in Command Prompt and look for the Physical Address field. On iPhones and some Android devices, Wi-Fi MAC randomisation may be active; you'll need to disable it for that network in the device's Wi-Fi settings before creating a reservation, otherwise the MAC address changes and the reservation won't match.
No — each reserved IP address must map to exactly one MAC address, and each MAC address can only appear once in the reservation table. Assigning the same IP to two MAC addresses would cause an IP conflict the moment both devices are online simultaneously, resulting in neither device having reliable connectivity. Always assign a unique address to each device you want to reserve.
You don't technically have to, but it is strongly recommended. Port forwarding rules target a specific local IP address, and if that address changes because the device's DHCP lease expired and it received a new one, the forwarding rule silently stops working. Setting up a DHCP reservation first ensures the device always has the same address and your port forwarding rules remain valid indefinitely.
If you reserve an address that another device currently holds via a dynamic lease, a conflict will occur when both devices are online — typically resulting in one or both devices losing network access. To avoid this, always pick a reserved address from outside your router's active DHCP pool range, or check your router's current lease table to confirm the address isn't already in use before saving the reservation.
For authoritative networking standards and specifications, refer to the Internet Assigned Numbers Authority (IANA) or IETF RFC documents.
 |
 |
 |
 |
About Tommy N.
Tommy is the founder of RouterHax and a network engineer with over ten years of experience in home and enterprise networking. He has configured and troubleshot networks ranging from simple home setups to multi-site enterprise deployments, with deep hands-on experience in router configuration, WiFi optimization, and network security. At RouterHax, he oversees editorial direction and covers home networking guides, mesh WiFi system reviews, and practical troubleshooting resources for everyday users.
Promotion for FREE Gifts. Moreover, Free Items here. Disable Ad Blocker to get them all.
Once done, hit any button as below
|
|
|
|
