Static IP vs. dynamic IP: what's actually different
Quick answer
A static IP stays assigned to your server or service until you deliberately change it. A dynamic IP can change on its own, typically on reboot or when a lease from a shared pool expires, because it was never permanently yours to begin with. For hosting, that difference matters well beyond convenience: DNS, reverse DNS and mail reputation, firewall allowlists, and some software licences all quietly assume the IP behind them doesn't move.
The core difference
Every device on a network needs an IP address to be reachable, but how that address is assigned differs. A dynamic IP is handed out from a shared pool, usually via DHCP, for a limited lease. When the lease expires, or the device reboots and requests a new one, it can come back with a different address than before; this is the normal, expected behaviour on something like a home broadband connection, where the ISP manages a pool of addresses across many customers. A static IP is assigned once and stays assigned. It doesn't change on reboot, and it doesn't get silently handed to someone else, because it isn't drawn from a rotating pool in the same way.
Why static matters specifically for hosting
A server that changes address on its own is a problem for anything that depends on that address staying fixed, and hosting is full of exactly that kind of dependency.
- DNS records. A domain's A record points at a specific IP. If that IP changes underneath the record, every visitor following that domain name starts failing to reach the server until the record is manually updated and has propagated.
- Reverse DNS and mail reputation. Mail servers build a sending reputation against a specific IP over time, and many receiving mail systems check that the IP's reverse DNS matches the sending domain. An IP that changes resets that reputation and breaks the reverse DNS mapping, which is a common, avoidable cause of outbound mail suddenly landing in spam.
- Firewall allowlisting. Where another system, a partner API, an internal network, a third-party service, allowlists your server's IP specifically, a changed IP silently locks you out until someone updates the allowlist on the other end.
- Licensing. Some software licences are tied to a specific IP address as part of how they validate the install. A changed IP can invalidate that licence until it's reactivated against the new address.
None of these break because a dynamic IP is inherently unreliable as a piece of networking. They break because so much of the surrounding infrastructure, DNS, reputation, allowlists, licences, is built on the assumption that a server's address is a fixed point of reference, not something that shifts on its own.
What to expect by default
As a general pattern across the hosting industry, dedicated servers and most VPS or cloud instances are typically assigned a static IP by default, in contrast to something like home broadband, where a dynamic, pool-assigned IP is the norm. That's a reflection of what hosted infrastructure is generally used for: servers are meant to be reachable at a consistent, known address, which is exactly the property DNS, mail, and firewall configuration all depend on.