Static IP vs Dynamic IP

Every device on an IP network needs an address. You can assign that address by hand, or let a server hand it out automatically. Static IP addressing means you configure an address by hand and it stays fixed, while Dynamic IP addressing uses the Dynamic Host Configuration Protocol (DHCP) to lease addresses to clients automatically from a pool.

In this lesson, you’ll learn the difference between static and dynamic IP assignment. You’ll also learn when each method is the better choice for a given device or network.

Key Takeaways

• Static IP addressing means you manually assign an IP address, subnet mask, gateway, and DNS settings. This stays fixed until an administrator changes it.
• Static addressing has no built-in conflict detection. Administrators must track assignments manually to avoid duplicate IP addresses on the network.
• Static addressing suits devices that need predictable, unchanging addresses, such as servers, printers, routers, and switches. It doesn’t scale well for large numbers of hosts.
• Dynamic IP addressing uses DHCP to automatically assign addressing information from a server-managed pool, or scope, of available addresses.
• DHCP distributes the IP address, subnet mask, gateway, DNS, and other options as a lease, not a permanent assignment, and clients renew or release it periodically. This reduces manual configuration errors and prevents IP address conflicts.
• Dynamic addressing scales well in environments with many hosts or frequent changes, such as laptops, mobile devices, and guest networks.
• Choosing between static and dynamic addressing depends on administrative effort, scalability, and how important predictability is for the device or environment.
• DHCP reservations combine both approaches: DHCP assigns a fixed address to a specific device based on its MAC address.

Prerequisites

To follow this lesson, you should understand IPv4 addressing, including how an IP address, subnet mask, and default gateway let a host communicate on a network. You should also be familiar with how DHCP automatically assigns these settings to clients.

Static IP Addressing

Static IP addressing is the manual, permanent assignment of an IP address, subnet mask, gateway, and DNS settings to a device.

You configure the address manually on the host or device interface, and it doesn’t change unless an administrator changes it. Because static addressing has no built-in conflict detection like DHCP offers, administrators must track assignments manually to avoid duplicate addresses on the network.

Static addressing is typically used for devices that need predictable, unchanging addresses, such as servers, printers, and network infrastructure devices like routers and switches. However, administrative overhead scales poorly with large numbers of hosts, since you have to configure and document every device individually.

Static addressing applies at any layer, not just the LAN. Giving a device a static private address on your LAN (for example, 192.168.1.10 on a server) is separate from whether your router’s WAN address, the public IP assigned by your ISP, is static or dynamic. A static public IP is usually a paid, separately configured service used for hosting, remote access, or port forwarding (redirecting inbound traffic on a specific port to a device inside the LAN). It has no bearing on how devices are addressed inside your own network.

Dynamic IP Addressing (DHCP)

Dynamic IP addressing relies on DHCP to assign addressing information to clients automatically, without manual intervention.

The DHCP server maintains a pool, or scope, of available addresses and assigns addresses to clients on request. It automatically distributes the IP address, subnet mask, gateway, DNS, and other options, which reduces configuration errors compared to manual entry.

Addresses are leased, not permanently owned by the client, so the client must renew or release the lease over time. In practice, a client usually keeps the same address across renewals, unless it’s been off the network longer than the lease time or another client needed the address. “Dynamic” describes how the address is assigned, not how often it changes.

Dynamic addressing is well suited to environments with many hosts or frequent changes, such as laptops, mobile devices, and guest networks.

If the DHCP server goes down, existing clients keep working until their lease needs renewal: a device with an active lease keeps using its address normally while the server is unavailable. A new device, or one whose lease expires or needs renewal during the outage, fails to get an address, and may fall back to an Automatic Private IP Addressing (APIPA) address.

Comparison

These are the practical criteria you use to decide between static and dynamic addressing in a given scenario: administrative effort, scalability, predictability and stability of addressing, and risk of address conflicts. The table below summarizes how static and dynamic addressing compare across each of these factors.

A manually configured static IP, a DHCP reservation, and a regular dynamic pool assignment are three distinct categories, not two. A reservation ties a specific address to a device’s MAC address (the fixed hardware address burned into a network interface) on the DHCP server, so the device always gets the same address. It still goes through the same discover, offer, request, and acknowledge exchange as any other client on every boot, and it still depends on the DHCP server being reachable. We cover configuring reservations in our own lesson on DHCP static binding on Cisco IOS.

Checking Whether an Address Is Static or Dynamic

To tell whether an address was assigned statically or dynamically, check the interface configuration, not the address itself. I’ll give you some examples.

Windows

On Windows, it is easy to see:

C:\Users\user>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Windows
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 7:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Ethernet Controller X710 for 10GbE SFP+
   Physical Address. . . . . . . . . : 3C-FD-FE-E5-50-C1
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::c91d:da7f:92dc:784d%29(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.65.20.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.65.20.254
   DHCPv6 IAID . . . . . . . . . . . : 524090878
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2E-EE-13-48-60-CF-84-AC-C9-48
   DNS Servers . . . . . . . . . . . : 10.65.10.30
                                       10.65.10.31
   NetBIOS over Tcpip. . . . . . . . : Enabled

This will output DHCP Enabled and shows either No (static) or Yes (DHCP).

Linux

On Linux there are different ways to look at assigned IP addresses. A common one is the ip command. Here is a static IP address:

# ip -4 addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    altname enp0s18
    inet 192.168.12.40/24 brd 10.65.90.255 scope global eth0
       valid_lft forever preferred_lft forever

You can’t really tell that this is a static IP address unless you know that it lacks the word “dynamic” which does show up when it’s a dynamic IP address:

# ip -4 addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    inet 79.12.13.146/32 metric 100 scope global dynamic eth0
       valid_lft 77368sec preferred_lft 77368sec

Above, you can see it showsdynamic, which means it was assigned through DHCP.

Cisco

On Cisco devices, there are also multiple ways to see assigned IP addresses. Here is a static IP address:

R1#show ip interface brief
Interface              IP-Address      OK? Method Status                Protocol
Ethernet0/1            192.168.12.1    YES manual up                    up      
Ethernet0/2            unassigned      YES unset  administratively down down    
Ethernet0/3            unassigned      YES unset  administratively down down 

This tells us the method is manual. And here is an example of a DHCP-assigned IP address:

R2#show ip interface brief
Interface              IP-Address      OK? Method Status                Protocol
Ethernet0/1            192.168.12.2    YES DHCP   up                    up      
Ethernet0/2            unassigned      YES unset  administratively down down    
Ethernet0/3            unassigned      YES unset  administratively down down

This one shows DHCP for the method.

Conclusion

You’ve now learned the difference between static IP addressing and dynamic IP addressing.

We compared manual configuration of the address, subnet mask, gateway, and DNS settings against DHCP-based assignment. We also looked at when each method fits best. Along the way, we saw how DHCP reservations combine the two: they give a device a consistent address while still depending on the DHCP server. Finally, we covered how to check whether an interface uses a static or dynamic address.