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.

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.

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.

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.

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.