Static IP vs Dynamic IP Address

A static IP address is a network identifier permanently assigned to a device that remains constant across all sessions — configured manually by an ISP or network administrator, it never changes unless deliberately reconfigured. A dynamic IP address is automatically assigned from an available address pool by a DHCP server (RFC 2131) and returned to the pool when the lease expires. Static IPs suit servers, VPNs, and hosted services requiring a fixed endpoint. Dynamic IPs are the residential and small-business default — lower cost, automatically managed, and transparent to most users.

A static IP never changes: it is set by hand on the device, or reserved for you by your ISP.

A static IP address is an internet or network address permanently fixed to a specific device or service. Unlike addresses issued through DHCP, a static IP is either manually entered into a device's network adapter configuration or reserved by the ISP so that the same address is always returned to that customer.

From an infrastructure standpoint, static IPs are essential when external systems need to reach a service at a predictable, unchanging address. A web server must have a static IP so its DNS A record remains valid indefinitely. A mail server requires one because receiving mail servers verify the PTR (reverse DNS) record of the sending IP — a changing address breaks this verification and causes delivery failures. A corporate VPN endpoint must have a static IP so that firewall access-control rules, which whitelist specific addresses, do not break each time the IP rotates.

Two distinct types exist:

• Static public IP — Assigned at the WAN level by the ISP, visible to the internet. Requires a service upgrade or additional monthly fee.
• Static private IP (DHCP reservation) — Configured within a local network by binding a specific local address to a device's MAC address in the router's DHCP reservation table. Free — no ISP involvement required.

Cost of a Static IP Address

Static public IPs are not included in standard residential internet plans. ISPs typically charge an additional $5–$30 per month for a dedicated static IP on residential connections; business-grade plans with multiple static IPs cost more. Some ISPs require upgrading to a business account entirely before a static IP becomes available.

A dynamic IP is lent to your device by a DHCP server and can change over time. Most home connections use one.

A dynamic IP address is one automatically issued by a DHCP server (Dynamic Host Configuration Protocol, RFC 2131) each time a device requests network access. The address is drawn from a pool of available addresses maintained by the server — at the ISP level for public WAN IPs, or at the router level for private LAN addresses.

Dynamic addressing exists primarily to conserve the finite IPv4 address space. With approximately 4.3 billion total IPv4 addresses and far more connected devices worldwide, ISPs cannot permanently dedicate one address per customer. Dynamic allocation reclaims addresses from offline or idle devices and reassigns them to active connections, maximizing pool utilization.

The DHCP DORA Handshake

When a device requests a dynamic IP, DHCP uses a four-message exchange known as DORA:

1. Discover — The device broadcasts a DHCPDISCOVER packet on the local network segment, looking for available DHCP servers.
2. Offer — A DHCP server responds with a DHCPOFFER, proposing an available IP address along with lease duration, subnet mask, default gateway, and DNS server addresses.
3. Request — The device accepts by sending a DHCPREQUEST, confirming which server's offer it is accepting (relevant when multiple DHCP servers respond).
4. Acknowledge — The DHCP server sends a DHCPACK, confirming the lease. The device applies the configuration immediately and begins using the assigned address.

A dynamic IP comes with a lease. The device tries to renew it at 50% of the lease time (T1), asks any DHCP server at 87.5% (T2), and must stop using it when the lease expires.

Every dynamic IP assignment includes a lease time — the duration for which the address is reserved for that specific device. RFC 2131 Section 4.4 defines two renewal thresholds that govern what happens before and after that timer runs out:

• T1 (50% of lease time) — The device sends a unicast DHCPREQUEST directly to the issuing DHCP server to renew the same IP before it expires. This is the normal renewal path.
• T2 (87.5% of lease time) — If the T1 unicast renewal receives no response (server unreachable), the device broadcasts a renewal request to any available DHCP server on the network.
• Lease expiry (100%) — If neither T1 nor T2 renewal succeeds, the device releases the IP address and restarts the full DORA handshake to obtain a new address.

Typical lease durations vary significantly by network type:

• Residential ISP (cable / fiber): 24 hours to 8 days
• Home router local DHCP: 24 hours (firmware default on most consumer routers)
• Enterprise LAN: 4–8 hours (shorter leases improve address pool turnover)
• Mobile carrier networks: 1 hour or less (very high churn rate)

Sticky DHCP — Why Your IP Often Stays the Same

Most home users observe that their dynamic IP rarely changes despite technically holding a time-limited lease. ISPs implement sticky DHCP by binding a lease to the customer's modem MAC address or DHCP Unique Identifier (DUID). The DHCP server consistently renews the same address to the same device as long as the lease is renewed on schedule. The address is not permanently reserved — a prolonged disconnection, ISP maintenance event, or modem replacement can break the binding and result in a new IP assignment. Sticky DHCP is not the same as a paid static IP; the ISP makes no contractual guarantee of address persistence.

Dynamic DNS (DDNS) as a Hosting Workaround

Hosting a server from a residential connection with a dynamic IP requires a Dynamic DNS service — providers such as No-IP, Duck DNS, and Cloudflare offer this. DDNS automatically updates a hostname's DNS A record whenever the underlying IP changes, maintaining a consistent domain name for incoming connections. This approach adds operational complexity and introduces a propagation delay between IP change and DNS update, which is why static IPs remain strongly preferred for any production-grade hosted service.

Use a static IP when other systems must always find you at the same address: web and mail servers, VPN endpoints and IP allowlists.

A static IP is necessary or strongly recommended in the following four scenarios:

Web and mail servers. Any device hosting a website, API, or mail service must have a static IP so that DNS records remain valid. A rotating IP breaks DNS resolution — visitors cannot reach the service until the old TTL expires and propagation completes to the new address, which can take hours.

Reverse DNS and email deliverability. Mail servers require a valid PTR record — a reverse DNS entry mapping the sending IP to the mail server's hostname. Providers including Google, Microsoft, and most enterprise mail gateways reject or quarantine mail from servers without a matching PTR record. PTR records can only be reliably set against a static IP; they break immediately if the address changes.

VPN endpoints and firewall whitelists. Corporate VPN configurations and firewall access-control rules are typically locked to specific IP addresses. A rotating dynamic IP forces administrators to update rules each time a remote worker's IP changes — creating management overhead and creating temporary access gaps.

IP address whitelisting. Some banking, financial, and enterprise systems restrict access to specific whitelisted IPs. Users on dynamic IPs who are whitelisted may lose access silently when their address rotates, requiring re-authentication with IT each time.

When a dynamic IP is sufficient. For home internet use — streaming, gaming, browsing, video calls, and consuming cloud-hosted applications where the cloud provider owns the static endpoint — a dynamic IP delivers full functionality at no additional cost. The vast majority of residential users have no practical need for a static IP.