The Three Systems Behind Every Connection
When you type a web address into your browser and press Enter, a sequence of events unfolds in well under a second. Three distinct systems — IP addressing, DNS, and DHCP — coordinate seamlessly so that your request reaches the right server and the response finds its way back to you. None of these systems is visible during normal use, but any one of them failing is enough to make the internet feel completely broken.
To understand your home network — and to troubleshoot it intelligently when things go wrong — it helps to know what each system actually does. See our guide to how your home network works for the broader picture of how these pieces fit together physically.
~4.3 billion
Maximum unique IPv4 addresses available globally
The 32-bit IPv4 address space was essentially exhausted by regional internet registries between 2011 and 2019, driving the shift to IPv6.
340 undecillion
Unique IPv6 addresses possible
IPv6's 128-bit address space provides approximately 3.4 × 10³⁸ unique addresses — enough to assign trillions to every person on Earth.
< 100ms
Typical DNS lookup resolution time
A full recursive DNS lookup generally completes in under 100 milliseconds; cached responses resolve in single-digit milliseconds.
IP Addresses: Every Device Needs a Location
An IP address (Internet Protocol address) is a numerical label that identifies a specific device on a network. Think of it as a postal address: without one, there's no way to direct data to the right destination or know where a reply should go.
Most home networks use IPv4 addresses — four groups of numbers separated by dots, such as 192.168.1.42. Each device on your local network gets a private IP address in this format. Your router also holds a separate public IP address — the one your internet service provider assigns — which is what the outside world sees when your devices communicate online.
Because the pool of available IPv4 addresses is finite, a newer standard called IPv6 was developed. IPv6 uses a longer alphanumeric format that provides vastly more unique addresses, accommodating the billions of internet-connected devices now in use. Most modern routers and networks support both formats simultaneously.
Understanding how speed and latency interact with your connection becomes more meaningful once you know that every data packet traveling across the internet is tagged with a source and destination IP address at every hop.
DNS: The Internet's Phone Book
Humans remember names; computers route by numbers. DNS — the Domain Name System — bridges that gap. When you type example.com into your browser, a DNS resolver (typically operated by your internet service provider, or one you've configured manually) looks up the IP address associated with that domain name and returns it to your device. Your browser then uses that IP address to connect to the correct server.
This lookup happens through a hierarchy of servers. A recursive resolver accepts your query and works through the hierarchy if it doesn't have the answer cached. It first contacts a root nameserver, which directs it to a TLD (top-level domain) server for extensions like .com or .org. That server points to the domain's authoritative nameserver, which holds the actual IP address record. The resolver returns this address to your browser and caches it briefly so repeat visits skip the full lookup.
DNS caching is why a site change sometimes takes time to propagate — your device or resolver may still be using a cached, outdated record. Clearing your DNS cache or waiting out the TTL (time-to-live) period resolves this.
Worth noting: DNS queries are also a privacy consideration. Your resolver can log every domain you request. Encrypted DNS protocols (DNS-over-HTTPS and DNS-over-TLS) prevent third parties from reading those queries in transit. This connects directly to broader questions covered in our digital privacy primer.
DHCP: Automatic Address Assignment
DHCP — Dynamic Host Configuration Protocol — is what makes joining a network effortless. Without it, every device would need to be manually assigned an IP address, a subnet mask, a default gateway, and DNS server addresses before it could communicate. DHCP automates all of that in seconds.
When a device joins a network, it broadcasts a discovery message. The DHCP server (usually built into your router) responds with an available IP address offer. The device accepts the offer, and the server formally acknowledges the assignment — a four-step exchange known as DORA: Discover, Offer, Request, Acknowledge.
IP addresses assigned through DHCP come with a lease duration — a time limit after which the device must renew or release the address. This allows the network to reclaim unused addresses and reassign them, keeping the available pool fresh.
For devices that need a consistent, predictable address — a network printer, a media server, a smart home hub — you can configure a static IP address manually or use a DHCP reservation, which tells the router to always assign the same address to a specific device based on its hardware identifier.
Use DHCP Reservations for Smart Home Devices
Smart home hubs, network printers, and media servers work more reliably when their IP address doesn't change between reboots. Instead of configuring a fully manual static IP (which risks conflicts), use your router's DHCP reservation feature — it instructs the DHCP server to always assign the same address to a specific device based on its MAC address. This combines the consistency of a static address with the safety of managed assignment.
What This Means for Everyday Troubleshooting
When your internet connection seems broken, knowing which system has failed narrows the diagnosis considerably. If you can reach a website by typing its IP address directly but not by its domain name, the problem is DNS — not your connection. If no device on your network gets an address, DHCP may have stalled, and restarting your router typically resolves it. If specific devices can't connect while others can, IP address conflicts or lease exhaustion may be the cause.
Running a home network audit periodically can surface configuration issues before they become noticeable problems — including outdated DNS settings, address pool limits, or router firmware that needs updating.
It's also worth remembering that these systems interact with privacy in ways that aren't always obvious. Your public IP address identifies your household to websites and services. Your DNS queries reveal your browsing patterns to your resolver. Even incognito mode doesn't mask either of those signals — a common misconception worth understanding before assuming you're browsing privately.
Frequently Asked Questions
An IP address is a numerical label assigned to each device on a network, functioning like a postal address for data. Without a unique IP address, a network has no way to direct traffic to the correct device. Both IPv4 (e.g., 192.168.1.10) and the newer IPv6 format exist to handle the enormous number of internet-connected devices worldwide.
That brief pause is largely the DHCP process in action. Your device broadcasts a request for an IP address, the DHCP server responds with an offer, your device accepts it, and the server confirms — a four-step exchange that takes only seconds but is essential before any data can flow.
If the DNS server your device uses goes offline, domain names can't be resolved into IP addresses, so websites appear unreachable — even though the internet connection itself is technically fine. Switching to an alternative DNS server in your network settings can restore access quickly.
Private IP addresses are used within your home network (e.g., 192.168.x.x) and are assigned by your router's DHCP server to each device. Your router holds a single public IP address assigned by your internet service provider — that's the address the rest of the internet sees when your devices go online.
Yes. A static IP address is manually configured and doesn't change, which is useful for devices like printers or network storage that benefit from a predictable address. DHCP is more practical for most consumer devices since it handles address management automatically without risk of conflicts.
Yes — your DNS resolver can see every domain name you request, which is a log of nearly every site you visit. Some resolvers offer DNS-over-HTTPS (DoH) or DNS-over-TLS (DoT) to encrypt those queries. For a broader look at online privacy, see <a href="/tech-explained/software-apps/digital-privacy-from-the-ground-up-a-consumers-starting-point">our consumer privacy starting point</a>.
The content on this site is for informational purposes only and is not a substitute for professional advice. Always consult a qualified professional for guidance specific to your situation.