How the IP Address Is Assigned? | Who Picks It

Every phone, laptop, smart TV, game console, and server needs an IP address to send and receive data. That address is not pulled out of thin air. A device gets it through a set of rules that keeps traffic organized, avoids clashes, and tells other machines where to send packets.

If you’ve ever joined Wi-Fi and gone online in seconds, you’ve already seen this process in action. The network saw your device, picked an address that fit the local setup, handed over a few other settings, and let you start browsing. It feels instant on the surface. Underneath, a few moving parts are working together.

This article walks through who assigns IP addresses, what happens at home, what changes on office or school networks, where internet providers step in, and why the same device may keep one address one day and get a different one the next.

Why Every Network Needs A Clear Address Plan

An IP address is a label for routing. It tells the network, “send this traffic here.” Without that label, data has nowhere precise to go. Two devices with the same address on the same local network can trip over each other. No device with any address at all can’t join the conversation.

That’s why assignment is controlled. Someone or something has to decide which address is open, whether it belongs to the local network, how long the device can keep it, and which gateway and DNS settings go with it.

There are two broad ways this happens. One is automatic assignment, which most people use every day. The other is manual assignment, often called a static IP, where an admin enters the address by hand and keeps it reserved for one device.

How The IP Address Is Assigned? At Home And At Work

On most networks, the answer starts with DHCP, short for Dynamic Host Configuration Protocol. When your device joins the network, it asks for configuration. A DHCP server answers with an available IP address, a subnet mask, a default gateway, and often DNS server details too.

At home, your router usually plays DHCP server. In a company, school, or hotel, that job may be handled by a dedicated network server, a firewall, or a managed router. The device does not choose a random address and hope for the best. It asks, the network checks its rules, and the network replies.

The classic flow is simple. A device arrives and broadcasts a request because it does not yet know where the DHCP server is. The server offers an address from its pool. The device asks to use that address. The server confirms it and sets a lease time. That lease is the clock that says how long the address is valid before renewal.

This is one reason IP assignment feels smooth. A good network already has a range ready, knows which addresses are free, and can hand one out in a blink.

What The Router Is Really Doing

Your home router keeps a local address pool. A common setup might use a private range like 192.168.1.x, with some addresses reserved for the router itself and others open for phones, laptops, printers, and TVs. When a new device joins, the router picks an unused address from that pool.

The router also remembers which device got which lease. That way, when your laptop reconnects later, it often gets the same local address again. It is still dynamic, though. If the lease expires, the network is reset, or the pool changes, the device may get a different one.

What Changes On Managed Networks

Office and campus networks are stricter. The address a device gets may depend on the switch port, Wi-Fi SSID, user role, device type, or VLAN. A finance workstation may land in one subnet, a guest phone in another, and a printer in a third.

That split keeps traffic tidy and makes policy easier to enforce. It also means IP assignment is tied to network design, not just a first-come, first-served list of numbers.

Private Addresses, Public Addresses, And Who Controls Each One

A device usually deals with two layers of addressing: a private address inside the local network and a public address seen on the internet side. These are assigned by different actors.

Your local private IP is usually assigned by your router or internal DHCP server. Your public IP is usually assigned by your internet service provider. If you run a business connection, host services, or pay for a fixed public IP, your provider may assign one that stays the same much longer.

This split is why you can have a laptop with 192.168.1.24 at home while your home itself appears online under one public address shared through network address translation, or NAT. NAT lets many local devices ride through one public-facing address.

That public address does not come from your router’s imagination. Address blocks are distributed through global internet governance and regional registries, then routed down through providers. The reserved and special-use ranges are tracked in the IANA IPv4 special-purpose address registry, which is handy when you want to know why some addresses are private, loopback, documentation-only, or set aside for other protocol use.

Automatic Assignment Vs Manual Assignment

Automatic assignment is the default on modern networks because it scales well. Plug in a new device, and it gets what it needs. No one has to visit the settings screen and type numbers by hand.

Manual assignment is still common for devices that should stay easy to find, such as printers, NAS boxes, lab gear, cameras, or servers. A static address makes access rules cleaner and keeps bookmarks, monitoring tools, and port forwarding from breaking when a lease changes.

There’s also a middle ground: DHCP reservation. In that setup, the DHCP server still assigns the address, though it is told to hand the same one to the same device every time based on its MAC address or another identifier. This keeps the convenience of DHCP while giving one device a steady local address.

Assignment Method	Who Assigns It	Where It Fits Best
Dynamic via DHCP	Router or DHCP server	Homes, guest Wi-Fi, most employee devices
Static manual entry	Admin or user	Servers, printers, lab gear, fixed network devices
DHCP reservation	DHCP server using a saved rule	Devices that should keep one local address
Public dynamic IP	Internet provider	Most home internet plans
Public static IP	Internet provider with a fixed allocation	Hosted services, business links, remote access setups
IPv6 SLAAC	Router advertisement plus device self-configuration	IPv6 networks with light-touch local setup
IPv6 DHCPv6	DHCPv6 server	IPv6 networks that need tighter control
Link-local fallback	Device itself	Short-range local communication when no normal service is present

What Happens During DHCP Assignment

DHCP is the workhorse behind most IPv4 address assignment. The protocol is described in the official RFC 2131 DHCP specification, and its logic is still the base model behind many networks in use right now.

The exchange is often described in four steps:

1. Discover: the device asks whether any DHCP server is available.
2. Offer: a server replies with a proposed address and settings.
3. Request: the device asks to use that offered address.
4. Acknowledge: the server confirms the lease and starts the timer.

The lease matters more than many people think. It lets addresses be reused. If a phone leaves the network and never comes back, that address can return to the pool later. That keeps the system efficient, especially on busy guest networks where devices come and go all day.

Leases also explain why your IP may change after a router reboot, an ISP reconnect, or a long offline gap. Nothing “broke.” The device simply asked again, and the network made a fresh choice from the pool it had at that moment.

How IPv6 Assignment Differs

IPv6 can still use DHCP, though the story is a bit wider. Many IPv6 networks use SLAAC, which stands for Stateless Address Autoconfiguration. In that setup, the router announces the network prefix, and the device forms its own address from that information.

That means the router is still part of the assignment path, even if it is not handing out the full address line by line like a classic DHCPv4 server. On some networks, DHCPv6 is added too, especially when admins want tighter control over records, DNS behavior, or policy.

IPv6 also changes the feel of address planning. The address space is so large that networks do not face the same squeeze seen in IPv4. That gives admins more room to segment networks cleanly without recycling small pools quite so tightly.

Why A Device Can Have More Than One IP Address

A single device may hold several addresses at once. A laptop can have an IPv4 address, one or more IPv6 addresses, a temporary IPv6 privacy address, and a loopback address used inside the device itself. If it runs a VPN, it may get another address inside that tunnel too.

So when someone asks, “what is my IP address?” the honest answer is often “which one?” The local LAN address, the public WAN address, and the VPN address can all differ at the same moment.

Why The Same Device Does Not Always Keep The Same IP

People often assume an address belongs to a device in a permanent way. Most of the time, it doesn’t. It belongs to the network’s current plan.

A device may get a new address because the DHCP lease expired, the router was reset, a reservation was removed, the device moved to another subnet, the provider rotated the public IP, or the connection changed from Wi-Fi to mobile data. In offices, policy changes can shift devices across network segments too.

That is normal behavior. The point of dynamic assignment is flexibility. The tradeoff is that the number may not stay still.

Reason An IP Changes	What Usually Triggers It	What You’ll Notice
Lease renewal with a new value	Old lease expired and another address was free	Local IP differs after reconnecting
Router reboot or reset	DHCP pool starts fresh	Several home devices get new local IPs
SSID or VLAN change	Device joins a different network segment	New subnet and fresh routing path
ISP public IP rotation	Provider reconnect or policy cycle	Public-facing address changes
Manual admin change	New static entry or reservation rule	Address stays fixed after the edit
VPN connection	Tunnel assigns its own address	Apps may see a different IP range

How Admins Keep Assignment Clean And Predictable

Good networks do not leave address assignment to chance. Admins carve out ranges for users, servers, printers, phones, guest devices, lab equipment, and management ports. They leave room for growth and keep static assignments outside the dynamic pool when needed.

They also track leases, reservations, subnet size, DNS records, and gateway settings together. An IP address on its own is just a number. It becomes useful when the rest of the network knows how to route it, name it, and apply rules to it.

On larger setups, IP address management tools are used to record all of this. On smaller setups, a careful spreadsheet and a sane DHCP scope can still do the job well.

What This Means For Everyday Users

If you are using home internet, your local IP is usually assigned by the router, and your public IP is usually assigned by the provider. If you are at work or school, the local address is often assigned by a central network service based on that place’s internal rules. If you manually type an address into device settings, you are bypassing automatic assignment and taking that job on yourself.

That is the real answer to how the IP address is assigned: the network decides, based on protocol rules, available address space, and local policy. The device asks. The network answers. Then traffic can move cleanly from one point to another.