A static IP address is an IP address that stays assigned to the same device or interface until an administrator deliberately changes it. In address configuration it is the opposite of a dynamic IP address, which a device leases automatically from a DHCP server and which may change when the lease ends or the device reconnects.
In networking, the term covers two related situations: a manually configured address entered directly on a host, and a fixed address delivered by the network, either through a DHCP reservation on a local network or as a permanent public address from an internet service provider. In all cases the defining property is predictability: other systems can rely on finding the device at the same address.
How a static IP address is configured
A manually configured static address requires the administrator to supply every parameter that DHCP would otherwise provide. Missing or inconsistent values are the most common reason a statically addressed device cannot reach other networks or resolve names.
The table below lists the parameters needed for a static IPv4 configuration and the consequence of getting each one wrong.
| Parameter | Example value | Effect if wrong |
|---|---|---|
| IP address | 192.168.1.20 | Conflicts or unreachable host |
| Subnet mask or prefix length | 255.255.255.0 or /24 | Host misjudges which addresses are local |
| Default gateway | 192.168.1.1 | No access beyond the local subnet |
| DNS servers | 192.168.1.1 or internal resolvers | Names fail to resolve while IP works |
| Search domain | corp.example | Short host names fail to resolve |
On Linux, static addresses are typically defined through Netplan, NetworkManager or systemd-networkd; on Windows through the adapter IPv4 properties or PowerShell; and on network equipment through the interface configuration. Whatever the tool, the settings are stored locally and survive reboots without contacting any server.
Static IP address compared with related methods
Several address configuration methods produce stable addresses with different trade-offs. The key distinction is where the address is defined: on the device itself, on a central server, or derived automatically from the network.
| Method | Where the address is defined | Stability | Management effort |
|---|---|---|---|
| Manual static address | On the device | Fixed until changed by hand | High, one device at a time |
| DHCP reservation | On the DHCP server, keyed to MAC address | Fixed while the reservation exists | Low, central record |
| Dynamic IP address | DHCP pool, leased | May change at lease renewal | Very low |
| SLAAC address | Derived from the IPv6 router prefix | Stable or temporary, by design choice | Very low |
| Link-local or APIPA address | Self-assigned by the host | Local link only, not routable | None, used as a fallback |
Many administrators prefer DHCP reservations over manual configuration for ordinary devices such as printers. The device still behaves like a DHCP client, but it always receives the same address, and all address records remain in one central place. Manual static configuration remains essential for the infrastructure that DHCP itself depends on.
Public static IP addresses from providers
Internet service providers usually assign residential customers a dynamic public address, and many now place them behind carrier-grade NAT, where several customers share one public IPv4 address. A static public IP address is typically offered as a business service or paid add-on, because public IPv4 space is scarce.
A static public address is needed when outside systems must initiate connections to a known address. Typical cases include hosting a mail or web server, terminating site-to-site VPN tunnels, and passing IP allowlists of partners or cloud services. Correct reverse DNS (PTR) records are often tied to static addresses and are important for mail delivery.
Cloud platforms provide an equivalent concept, often called an elastic or reserved public IP, which can be moved between virtual machines while remaining the same address to the outside world.
When to use a static IP address
Static addressing is a deliberate exception rather than the default. It suits devices that other systems must find without name resolution, or that must work when DHCP is unavailable.
| Device or situation | Recommended method | Reason |
|---|---|---|
| Router, firewall, gateway | Manual static address | Other hosts use it as their gateway |
| DHCP and DNS servers | Manual static address | They cannot depend on their own service |
| Network printer or NAS | DHCP reservation | Stable address with central management |
| Laptops and phones | Dynamic DHCP | They move between networks |
| Server reachable from the internet | Static public IP or cloud reserved IP | Firewall rules and DNS records point to it |
A sound practice is to exclude static addresses from the DHCP pool. For example, a /24 network might reserve .1 to .49 for infrastructure and hand out .50 to .250 dynamically, which prevents the DHCP server from leasing an address already in use.
Risks and common mistakes
Static addressing shifts responsibility from software to people, and the typical failures reflect that. Documentation and consistent address plans are the main safeguards.
- IP address conflicts occur when a manually assigned address overlaps the DHCP pool or another static device; hosts detect some conflicts through ARP or Duplicate Address Detection, but not all.
- Stale settings persist after network changes, such as a new gateway or DNS server, because static hosts never receive updated parameters.
- Moved devices fail silently when a statically configured laptop joins a different subnet and cannot reach its configured gateway.
- Security through a fixed address is weak: a known, unchanging address makes a host easier to target, so firewalling and patching remain essential.
- IPv6 differs: hosts often hold several addresses at once, so a static IPv6 address coexists with link-local and possibly SLAAC addresses.
Keeping an IP address management record, even a simple spreadsheet in small networks, is the most effective way to avoid conflicts and to know which devices depend on fixed addresses.
A plain-language summary
Every device on a network needs an address so that data can find it, much like a house needs a street address. Most devices get a temporary address handed out automatically, which can change from time to time.
A static IP address is a permanent address that does not change. It is used for devices that others must always find in the same place, such as the office router, a shared printer or a server that customers connect to.
An example from practice
A small accounting firm with twenty employees uses the 192.168.10.0/24 network. The administrator assigns manual static addresses to the firewall at .1 and to a file server at .10, creates DHCP reservations for two printers at .21 and .22, and sets the DHCP pool to .100 through .200 for laptops and phones.
The firm also buys a static public IP address from its provider so that the tax software vendor can add it to an allowlist and so that staff can connect through a site-to-site VPN from a branch office. When the provider’s router is replaced, the public address stays the same, and no partner or VPN configuration needs updating.