Definition and basic model

A Dynamic IP address is assigned automatically by a DHCP service (commonly running on a router or network gateway). A Static IP address is configured so the device uses fixed network settings, rather than requesting a new assignment each time it reconnects.

In practice, “switching from dynamic to static” usually means you either:

  • change the network settings on your device or router so the device uses a fixed IP, or
  • use a feature like a DHCP reservation (where the DHCP server still assigns an address, but it stays consistent for your device).

What you need before you change anything

To set a static IP correctly, you generally need network parameters that match your local network. Common items include:

  • the IP address you want to assign (chosen to be compatible with your subnet)
  • the subnet mask
  • the default gateway
  • DNS server settings (either specific DNS IPs or a choice to use the gateway/router)

Also check whether your network uses DHCP-managed addressing for most devices. On some managed or corporate networks, you may not be allowed to set static IPs yourself; you might need network administrator permission.

Step-by-step options (where the change happens)

Option 1: Configure static IP on your device

If you control the device’s network settings, you can switch it from “Obtain an IP address automatically” (dynamic/DHCP) to “Use the following IP address” (static), then enter the values for IP, subnet mask, default gateway, and DNS.

After saving, reconnect the network (or restart the interface) and confirm the device now reports the intended IP address.

Option 2: Configure static behavior on the router (DHCP reservation)

If you want the assigned address to remain stable while still using DHCP, some routers offer “DHCP reservation” for a specific device identifier. This keeps the device’s address consistent without manually setting all static parameters on the device.

This approach is especially useful when you want fewer configuration mistakes on the client side and still need consistent addressing.

Option 3: Configure static IP on the router (for special setups)

Some networks use provider-managed settings or advanced routing setups where the “static” concept may be configured upstream or on a gateway device. In that case, the key distinction is still the same: your fixed addressing must be consistent with routing and subnet boundaries.

Differences, limits, and when the answer changes

Key limits can change what you should do:

  • Local vs public static: switching to a static IP on your device usually affects your local network (LAN) address; a public-facing static IP depends on what your internet provider offers.
  • IP conflicts: if you pick an IP address that is also in the DHCP pool or used by another device, you can cause connectivity problems.
  • Managed networks: some environments only allow dynamic IPs, or they require an administrator to register static settings.
  • DNS mismatch: even with the correct IP and gateway, wrong DNS values can make websites/services appear broken.

A practical exception: if your goal is “the same address every time,” DHCP reservation often achieves that stability with less risk than manually configuring static parameters on each device.

Practical checks you can do to confirm it worked

  1. Verify the current IP address on the device after the change.
  2. Check the subnet and gateway consistency (your device should be using the gateway that routes traffic to other networks).
  3. Confirm name resolution by checking that DNS is working (for example, whether domain names resolve, not just IP connectivity).
  4. Ensure no conflict exists by observing whether connectivity becomes unstable right after applying the static settings.

Because routers and operating systems label settings differently, the exact menu names vary. If you tell me your router model and whether you’re configuring a home LAN or a managed network, I can help map these steps to the exact fields you’ll see.