Should You Use a Static IP or a DHCP Reservation?

For most devices on a home or small-business network, a DHCP reservation is the better choice. The router assigns the same IP address every time the device connects, and you configure nothing on the device itself. A manual static IP — set directly on the device — is only worth the extra steps when your router does not support reservations, or when the device needs a fixed address that must travel with it to networks where you do not control the DHCP server.

What Each Method Actually Does

Both approaches give a device a stable, predictable IP address, but they operate at different layers of your network.

A DHCP reservation — sometimes called a static DHCP mapping, address binding, or IP/MAC binding depending on your router brand — lives entirely inside the router. You register the device's MAC address and pair it with a chosen IP. The device still uses the DHCP protocol normally; it just always receives the same answer. From the operating system's perspective nothing has changed: the address is still flagged as DHCP-assigned, leases renew automatically, and the router's conflict-tracking remains intact.

A static IP is configured on the device itself. You open the network adapter settings, disable DHCP, and manually enter an IP address, subnet mask, default gateway, and DNS servers. The router has no record of this assignment. The device announces its address without asking, and the DHCP server is completely unaware of it.

Why DHCP Reservations Win for Most Use Cases

Reservations have three concrete advantages over device-side static IPs:

• Single point of configuration. Set the reservation once in the router and every operating system — Windows, macOS, Linux, iOS, Android — gets the same predictable address without any per-device work.
• Built-in conflict prevention. The DHCP server tracks every address it issues. When you add another device to the network, the server will never hand out a reserved address to it.
• Centralised management. If you need to change the assigned address later, you edit one router entry. With static IPs you would need to log in to each affected device individually.

Printers, network-attached storage drives, IP cameras, game consoles, smart TVs, and streaming boxes are all natural candidates for a reservation. You want them reachable at a predictable address, but there is no reason to touch each device individually to achieve it.

How to Set a DHCP Reservation

Every router firmware labels the feature differently. Look for DHCP Reservations, Address Reservation, Static DHCP, or IP/MAC Binding under the LAN or DHCP settings section. Before opening your router's admin panel, confirm the actual gateway address rather than assuming:

Common gateway addresses are 192.168.0.1, 192.168.1.1, 10.0.0.1, and 192.168.2.1, but yours may differ. Open the address you find in a browser to reach the admin interface.

Steps that apply to most consumer routers:

1. Navigate to your router's admin interface in a browser using the gateway address.
2. Log in. Default credentials are usually printed on the router's label.
3. Open the DHCP or LAN settings section.
4. Find the reservations or static leases table.
5. Click Add and enter the device's MAC address and the IP you want to assign. You can find the device's MAC from its Wi-Fi or Ethernet settings, or from the router's active DHCP lease table.
6. Choose an IP inside your subnet but outside the dynamic DHCP pool range. Most routers display the pool start and end address on the same screen — pick something below the pool start to ensure no overlap.
7. Save and apply. Some routers require a restart to activate the change.
8. On the device, renew the DHCP lease to pick up the reservation immediately.

After renewal, confirm the device now shows the reserved address:

Brand-Specific Menu Paths

Firmware menus shift between versions. These paths reflect recent firmware at time of writing; if a label has moved, look under LAN or DHCP settings.

• TP-Link (tplinkwifi.net or 192.168.0.1): Advanced > Network > DHCP Server > Address Reservation
• ASUS (asusrouter.com or 192.168.1.1): LAN > DHCP Server > Manually Assigned IP around the DHCP list
• Netgear Orbi (orbilogin.com): Advanced > Setup > LAN Setup > Address Reservation
• Linksys (linksyssmartwifi.com or 192.168.1.1): Smart Wi-Fi Tools > DHCP Reservations
• Xiaomi (miwifi.com or 192.168.31.1): Settings > LAN Settings > DHCP Static IP

For OpenWrt: Network > DHCP and DNS > Static Leases — add the MAC address, hostname, and IP. For DD-WRT: Services > Services > Static Leases.

How to Set a Static IP on the Device

Use this method when your router does not support DHCP reservations, when the device will move between networks and needs the same address on all of them, or when you are on a hosted server or co-location rack where you have no access to the upstream DHCP server. Note that some ISP-provided gateway modems, particularly those operating in carrier-grade NAT ranges (100.64.0.0/10), may not expose a reservation interface at all — in that case, a static IP set on the device is your only option.

Before assigning any address, verify nothing already holds it. Ping it first:

A reply means that address is in use — pick a different one. Also check the ARP table for stale entries from devices that may have recently gone offline:

No ARP entry and no ping reply means the address is safe to claim.

Windows

Settings > Network & Internet > select your adapter > Edit IP assignment > Manual. Enter the IP address, subnet mask (255.255.255.0 for a standard /24 home network), default gateway, and preferred DNS server. Or from an elevated Command Prompt:

Replace Local Area Connection with your actual adapter name, which you can find by running netsh interface show interface.

macOS

System Settings > Network > select your interface > Details > TCP/IP tab. Set Configure IPv4 to Manually, then fill in the IP address, subnet mask, and router fields. DNS is a separate tab on the same Details sheet. Or via Terminal:

Linux (NetworkManager)

On Ubuntu 18.04 and later using Netplan, edit the relevant file under /etc/netplan/ and set the address under the interface block, then run sudo netplan apply. On Debian systems still using /etc/network/interfaces, set the interface to static and specify address, netmask, gateway, and dns-nameservers in the stanza for that interface.

iOS

Settings > Wi-Fi > tap the information icon next to your network name > Configure IP > Manual. Enter the IP address, subnet mask, and router. DNS is configured in a separate field on the same screen. The setting applies only to that specific network.

Android

Settings > Wi-Fi > long-press or tap the gear icon next to your network > Modify Network or Manage Network Settings (label varies by manufacturer and Android version) > Advanced Options > IP Settings > Static. Fill in IP address, gateway, network prefix length (24 for a /24 subnet), and DNS. After saving, disconnect and reconnect to apply the settings.

Which Method Should You Use?

Use this table as a quick reference:

• Home printers, NAS, IP cameras, game consoles, smart TVs: DHCP reservation. Configure once in the router; no device-side work needed.
• Servers on your own LAN: reservation works well. Only switch to a static IP if the server may move to a network where you cannot control the DHCP server.
• Hosted, VPS, or co-located servers: static IP is the only option; you do not control the upstream router.
• Laptops and phones that roam between networks: leave DHCP dynamic. Use per-connection profiles in the OS if you need fixed IPs on specific networks.
• Router does not support reservations: static IP on the device, chosen from outside the DHCP pool.

IP Conflict Risk and How to Avoid It

An IP conflict occurs when two devices on the same subnet claim the same address. Symptoms include intermittent connectivity drops on one or both devices, and Windows 10 and 11 will show a notification reading something like "there might be an IP address conflict" in the system tray.

Conflicts are most often caused by:

1. A static IP configured on a device that falls inside the router's dynamic DHCP pool, and the router later hands that same address to a different device.
2. A DHCP reservation was set, but the device still has an old static IP configured that was never cleared.
3. Two virtual machines sharing a host MAC address that maps to a reservation.
4. A device was replaced but the old MAC reservation was left in place; the same IP eventually gets re-issued from the pool to a new device.

The cleanest solution is to divide the subnet deliberately. Set your dynamic DHCP pool to start at a high number — for example 192.168.1.100 through 192.168.1.254 — and assign all reservations and any static IPs to the block below 192.168.1.100. This way a dynamic lease can never overlap a reserved address. Most routers let you adjust the pool start and end directly in the DHCP settings screen.

CLI Verification After Setup

Regardless of which method you used, confirm the result with these commands:

On Linux systems running systemd-resolved, resolvectl status shows the active DNS servers per interface and whether DNS over TLS is enabled — useful when configuring a server that needs a specific DNS policy alongside its fixed IP.

Common Misdiagnoses

• "My static IP keeps resetting." The device is still falling back to DHCP. Verify the IP assignment method is actually set to Manual or Static — not Auto. On mobile devices, this setting sometimes reverts when you forget and rejoin a network.
• "My reservation is not working." The existing DHCP lease has not expired yet. Force a renewal using the commands earlier in this article, or temporarily reduce the DHCP lease time in the router to a few minutes to accelerate expiry.
• "I can reach the IP but the hostname does not resolve." A fixed IP does not update DNS records automatically. You need to create or edit an A record by hand, or run a dynamic DNS client if the address may eventually change.
• "The device shows a 169.254.x.x address." That is an APIPA self-assigned address, which means the device could not reach the DHCP server at all. Setting a reservation or static IP will not help until the underlying network connectivity issue is resolved.
• "I set a reservation but the device got a different address." Verify the MAC address in your reservation matches what the device is actually sending. Android 10 and later, iOS 14 and later, and Windows 11 all use randomised MAC addresses by default for each network. Check your router's active lease table to see which MAC the device is presenting, and either update the reservation to match or disable MAC randomisation in the device's Wi-Fi settings for that specific network.

2026 Notes on IPv6, MAC Randomisation, and Encrypted DNS

Most networks now deliver both an IPv4 and an IPv6 address via DHCP. If you assign a fixed IPv4 address but leave IPv6 unconfigured or dynamic, the device may still route some traffic through a changing IPv6 path. Either configure IPv6 consistently — using a DHCPv6 reservation or a stable SLAAC address — or disable IPv6 on that adapter if it is not required.

MAC address randomisation is a deliberate privacy feature, enabled by default in Android 10 and later, iOS 14 and later, and Windows 11. These systems send a different MAC to each network, which silently breaks DHCP reservations tied to the hardware MAC. When a reservation stops working after an OS update, this is usually why. The fix: open your router's active DHCP lease table, find the MAC address the device is currently sending, and update the reservation to match. Alternatively, in the device's Wi-Fi settings for that specific network, look for a Privacy or MAC address type option and set it to use the device MAC rather than a randomised one.

DNS over HTTPS (DoH) and DNS over TLS (DoT) are now widely deployed in both enterprise and consumer routers. When you configure custom DNS servers alongside a fixed IP, confirm that the servers you specify support whatever encrypted DNS policy your router enforces. Google Public DNS (8.8.8.8) and Cloudflare (1.1.1.1) both support DoH and DoT. For a thorough explanation of how the DNS resolution chain functions from query to answer, Cloudflare's DNS overview is a reliable reference.