A fixed local address is useful for printers, NAS devices, home servers, cameras, controllers, and port-forward targets. The safest home-network method is often a DHCP reservation: the router’s DHCP server is told to offer a particular address to a particular client identity. This keeps address management centralized and avoids the common mistake of manually typing a static address that falls inside the dynamic pool and later collides with another lease.
What you are changing
Before reserving anything, confirm which device is the DHCP server and which client identity the router sees. Modern phones and laptops may use private MAC addresses per SSID, so a reservation tied to a different identity will not apply. For wired devices, the Ethernet MAC is usually stable, but some docks and adapters have their own address.
A safe step-by-step workflow
- Open the router or DHCP server and locate the connected-client/lease table.
- Identify the target device by hostname, current IP, and MAC address; verify the MAC on the device itself when possible.
- Choose an address inside the LAN subnet. Follow the router’s reservation model—some allow a reserved address inside the pool, while others expect reserved/static space outside the dynamic range.
- Create the reservation and save/apply the configuration.
- Renew the client lease or reconnect it so it requests a new lease.
- Verify that the device now receives the reserved address plus the expected gateway and DNS settings, then update any dependent service or port-forward rule.
What the evidence should tell you
A configuration step is complete only when you can verify both the intended effect and continued access to the rest of the network.
- Open the router or DHCP server and locate the connected-client/lease table. Record the before/after state so the change can be reversed.
- Identify the target device by hostname, current IP, and MAC address; verify the MAC on the device itself when possible. Verify this result before applying the next configuration step.
- Choose an address inside the LAN subnet. Follow the router’s reservation model—some allow a reserved address inside the pool, while others expect reserved/static space outside the dynamic range. If access is lost here, use the rollback path rather than stacking more changes.
- Create the reservation and save/apply the configuration. Record the before/after state so the change can be reversed.
- Renew the client lease or reconnect it so it requests a new lease. Verify this result before applying the next configuration step.
- Verify that the device now receives the reserved address plus the expected gateway and DNS settings, then update any dependent service or port-forward rule. If access is lost here, use the rollback path rather than stacking more changes.
A concrete example
On a 192.168.1.0/24 LAN, a NAS currently receives 192.168.1.143. You reserve 192.168.1.50 for its Ethernet MAC and renew the lease. The NAS can still use DHCP, but its address becomes predictable for backups, local bookmarks, and firewall rules. That is cleaner than hard-coding gateway and DNS values inside the NAS.
Prepare a rollback path first
Configuration work should be reversible. Before changing a router, gateway, DHCP scope, wireless policy, or firewall rule, record the current value and how you will regain local access if the new value is wrong. Save configuration exports when the platform supports them, but also keep a human-readable note of the settings that matter. Apply one meaningful change at a time and verify the result before moving to the next.
Deeper technical context
A reservation is not the same as a manually configured static IP. With a reservation, the client still uses DHCP; the server simply makes the outcome predictable. This means DNS and gateway changes can continue to propagate automatically. In larger networks, reservations also become documentation: you can see which addresses are intentionally pinned rather than reverse-engineering settings from every appliance.
Common mistakes that create bad conclusions
- Picking an address from a different subnet because it “looks unused.”
- Copying an IP currently used by another device.
- Binding the reservation to the wrong MAC when the client uses Wi-Fi MAC randomization.
- Assuming a reservation survives a router replacement without exporting or recreating the DHCP configuration.
Security and recovery notes
Use these steps only on networks and devices you own or are authorized to administer. Never weaken authentication, expose a management interface to the public internet, or publish router credentials merely to make troubleshooting easier. A normal reboot is very different from a factory reset: rebooting preserves configuration, while a reset can erase ISP, Wi-Fi, VPN, reservation, forwarding and segmentation settings. Prefer the least destructive test that can answer the question.
How to verify your conclusion
Do not stop at the first result that seems to confirm your theory. Repeat the decisive test after the change, compare it with a known-good client or path, and check that unrelated functions still work. For router changes, verify local management access, DHCP addressing, default gateway, DNS resolution, internet reachability and the specific feature you intended to fix. Keep the old setting in your notes until the network has remained stable long enough to trust the new state.
After the change: document the new normal
Once the network is stable, update your notes. Record the new subnet, reserved addresses, management URL, operating mode, Wi-Fi/security policy, and any exceptions you created. Remove temporary test rules such as broad DMZ entries, disabled firewalls, compatibility SSIDs, or bypass routes. A safe configuration is not only one that works today; it is one you can understand and recover six months later.
Questions people usually ask
Is a DHCP reservation permanent?
It remains effective while that DHCP configuration and client identity remain in place. It may need to be recreated after a router reset or replacement.
Should reservations be outside the DHCP pool?
It depends on the server. Many routers manage reservations inside the pool safely; others document a separate reserved range. Follow the device behavior.
Can I reserve by hostname?
Some systems display hostnames but usually bind the reservation to a MAC/client identifier.
Does this create a public static IP?
No. It fixes a private LAN address only. Public IP assignment is controlled by the ISP.
Bottom line
The useful outcome is not merely knowing the term or completing a setting change; it is being able to explain why the network behaved that way and reproduce the result safely. If the evidence points to a different layer than the one discussed here, follow the evidence rather than forcing the original theory.