IPAM glossary

What is a static IP address?

A static IP address (static Internet Protocol address) is an addressing method that gives a device a fixed IP address configured by an administrator. It is set manually on the device or through a DHCP reservation, and it remains the same across reboots and reconnections until someone changes it.

Let's simplify your DDI
Abstract isometric UI showing network ranges, usage bars, region names (EMEA/APAC), and a purple "Deploy" button
Key takeawaysKey takeaways are generated with AI assistance. Because automated summaries can occasionally contain errors or miss important context, always refer to the full blog post for complete information.

A static IP address is a fixed network address manually configured by an administrator that remains unchanged across device reboots and reconnections, providing predictable network access for critical infrastructure like servers, routers, and DNS/DHCP servers that other systems must reach at known locations. Unlike DHCP's automatic assignment from a pool with temporary leases, static addresses require manual configuration on the device or through DHCP reservations and must be carefully tracked in IPAM and DNS to avoid conflicts and operational issues. Proper management practices—including selecting addresses outside DHCP pools, documenting all assignments, and maintaining synchronized records—are essential to prevent address conflicts, connectivity failures, and administrative overhead during subnet changes or device migrations.

  • Static addresses must be excluded from DHCP scope ranges or explicitly reserved in IPAM to prevent the same address from being leased to multiple devices simultaneously, which causes intermittent connectivity and duplicate address warnings.
  • Address conflict detection per RFC 5227 and careful record-keeping in IPAM and DNS systems are critical operational safeguards that distinguish successful static IP deployments from those prone to failures during subnet renumbering and infrastructure changes.
  • True static addresses configured directly on devices work independently of DHCP server availability, making them essential for the DNS and DHCP infrastructure components themselves, whereas DHCP reservations maintain centralized server control while achieving similar operational results.

Static IP address at a glance

AttributeValue
Full namestatic IP address
CategoryAddressing method
Primary useGiving servers, network devices and other infrastructure a predictable, unchanging address
OSI layerLayer 3 (network layer)
Related termsDHCP, DHCP reservation, dynamic IP address, IPAM, DNS, IP address conflict

How static IP address works

A static address is not obtained through a negotiation. An administrator chooses the address and applies it, and the device uses it without asking a server for permission or a lease.

  1. Select an address: The administrator picks an unused address from the correct subnet. Checking an IPAM record first helps confirm that the address is not already in use.
  2. Configure the device: The address, subnet mask, default gateway and DNS server addresses are entered in the device's network settings, either by hand or by an automation tool.
  3. Exclude it from dynamic pools: The address should sit outside any DHCP scope range or be excluded from it, so a DHCP server never leases it to another device.
  4. Record it: The assignment is documented in IPAM and in DNS, so other administrators and systems can find the device by name.

A DHCP reservation reaches a similar result differently. The device still requests its address by DHCP, but the server always returns the same one for that client's identifier, usually its MAC address. This keeps configuration central. A true static address lives only on the device and does not change if the DHCP server is unavailable.

Why static IP address matters in enterprise networks

Servers, routers, firewalls, printers and DNS or DHCP servers themselves are commonly given static addresses because other systems must reach them at a known location. Static addressing also lets a device work when no DHCP server is reachable, which matters for the infrastructure that provides DHCP in the first place.

The cost is manual effort. Every static address must be tracked, and the settings must be correct on each device. The most common failure is an address conflict, where a static address overlaps a DHCP pool and the same address ends up on two devices. IPv4 hosts detect this with address conflict detection, described in RFC 5227, but the result is still intermittent connectivity for both devices. Stale spreadsheets and undocumented assignments make it worse, and renumbering a subnet means touching every statically configured device.

Security is also affected. A predictable address is easier for an attacker to target and easier to write into firewall rules, access lists and monitoring, so both defenders and attackers benefit from knowing it. Static addresses do not provide authentication. Teams that keep them tracked in IPAM, kept in sync with DNS, and separated from dynamic ranges avoid most of these problems.

Static IP address vs DHCP

A static IP address is fixed and set by an administrator, while DHCP assigns addresses automatically from a pool for a limited lease time. What is DHCP?

AttributeStatic IP addressDHCP
Assignment methodSet manually or through a reservationOffered by a server from a scope
Address stabilityStays the same until changedCan change when a lease expires and is not renewed
Administrative effortHigher, because each address is tracked and configuredLower, because the server handles assignment centrally
Dependence on a serverWorks with no DHCP server reachableRequires a reachable DHCP server or relay
Typical useServers, network gear, printersLaptops, phones, and other client devices
Risk of conflictHigher if records are not kept or the address sits inside a poolLower, since the server tracks the leases it issues

Common static IP address issues

A static address inside a DHCP scope range that was never excluded can be leased to another device. Symptoms include intermittent connectivity for both hosts, duplicate address warnings in operating system logs, and ARP entries that flip between two MAC addresses.

When static assignments are not recorded in IPAM or a spreadsheet, the next administrator picks an address that looks free but is in use. Decommissioned devices also leave addresses that stay reserved and never get reused.

Each static device carries its own gateway, mask, and DNS server entries. After a subnet renumbering or DNS server change, devices configured by hand keep the old values and lose name resolution or off-subnet reach until someone edits them.

A mask that does not match the subnet lets a host reach some neighbors but not others. The device may appear to work locally while traffic to part of the network fails, which makes the cause hard to spot.

Moving a server to another VLAN or site with its old static address leaves it unreachable, since the address no longer belongs to the local subnet. Firewall rules, DNS records, and allow lists that reference the old address also need updating.

See how unified DDI simplifies network operations

Manage DNS, DHCP and IP addresses from one platform with automation, visibility and control built in.

Talk to us

Static IP address FAQ

Related terms

Article

Dynamic IP Address

An IP address that changes from time to time, unlike a static IP address.

Learn more
Article

DHCP (Dynamic Host Configuration Protocol)

The standard mechanism to dynamically assign IP addresses within a network.

Learn more
Article

IPAM (IP address management)

A method for planning, tracking, and managing IP address space on a network.

Learn more
Article

Internet Protocol Address (IP Address)

A numerical label assigned to each device connected to a network that uses IP for communication.

Learn more
Article

Subnet mask

A 32-bit number that masks an IP address, and divides the IP address into network address and host address.

Learn more
Article

DORA process

The sequence of discover, offer, request, and acknowledge messages exchanged between client and server for DHCP.

Learn more
Article

IPv4 (Internet Protocol version 4)

The fourth version of Internet Protocol that uses 32-bit addresses to route most of today’s internet traffic; the global supply of IPv4 addresses is exhausted. Learn More

Learn more
Article

RFC 1918 networks

Ranges of IP addresses set aside for private use on TCP/IP networks.

Learn more
Browse the full glossary