A manually configured static address lives on the client: you type its IP, prefix/mask, gateway, and DNS settings into that device. A DHCP reservation lives on the DHCP server: the client still requests configuration automatically, but the server consistently offers the chosen address to that client identity. Both can make a printer or NAS predictable, yet they behave differently when the router, DNS, or subnet changes.

Static addressing and reservations have different owners

For many home networks, reservations are easier to manage because addressing intent is centralized on the router. Static configuration remains useful for infrastructure that must be reachable before DHCP exists or in designs where the administrator intentionally manages addresses outside DHCP. The key is to avoid accidental overlap and to document the choice.

Keeping a service reachable after lease renewal

A home server with a DHCP reservation at 192.168.50.20 can keep automatic DNS and gateway settings while remaining stable for local bookmarks. A router, managed switch, or critical controller might instead use carefully documented static infrastructure addressing if that suits the network design.

Choose where the stable address is managed

  • A reservation lets the router continue supplying gateway and DNS changes automatically.
  • A manual static address can keep working even if DHCP is down, provided the rest of the network still exists.
  • Reservations depend on client identity such as a MAC address, which can change with private-MAC features or different adapters.
  • Static addresses must be chosen outside conflicting dynamic assignment or explicitly excluded/reserved.
  • Both approaches are private-LAN choices and do not create a public static IP from the ISP.

Lease pools, identity and replacement devices

Address stability is only one part of service stability. If local DNS can resolve a NAS hostname, you may not need users to remember its numeric address at all. Conversely, firewall and port-forward rules often work best with a predictable destination. Good network design uses the simplest stable identifier that the dependent service actually needs.

Prevent duplicate IP assignments

  • Using the term “static IP” without specifying LAN or public/WAN context.
  • Hard-coding DNS and gateway on many clients, then forgetting them during a router change.
  • Reserving an address for the wrong randomized/private MAC identity.
  • Leaving manually static addresses undocumented inside the DHCP pool.

Which is better for a printer?

Usually a DHCP reservation is convenient because it centralizes management, but a well-documented static address also works.

Does a reservation require the device to use DHCP?

Yes. The server recognizes the client and offers the reserved address.

Can a static IP cause a conflict?

Yes if another device or the DHCP server assigns the same address.

Is a public static IP the same thing?

No. Public address assignment is an ISP service and is separate from LAN addressing.