Everything You Need to Know About IP Addresses
A plain-English guide to IP addresses — IPv4 vs IPv6, public vs private, static vs dynamic, subnet masks, DNS, DHCP and NAT — the networking core every IT beginner has to know.
Short answer: an IP address is the unique number that identifies a device on a network, so data knows where to go — like a mailing address for your computer. Every phone, laptop, server, and smart bulb that talks to a network has one. Understanding IP is the single most useful networking skill you can build early in an IT career, and it shows up all over the CompTIA A+ and Network+ exams. This guide covers all of it in plain English.
What an IP address actually is
IP stands for Internet Protocol — the set of rules that governs how data moves across networks. An IP address is the identifier those rules use. When your laptop requests a web page, two addresses are involved: yours (so the answer can come back) and the server’s (so the request gets there). No IP, no conversation.
There are two versions in use today — IPv4 and IPv6 — and you need to recognize both.
IPv4 vs IPv6
IPv4 is the original and still the most common. It’s a 32-bit number written as four decimal octets separated by dots, each ranging 0–255:
192.168.1.10
That gives about 4.3 billion unique addresses — which sounded infinite in the 1980s and ran out years ago. The fix is IPv6, a 128-bit address written as eight groups of hexadecimal, separated by colons:
2001:0db8:85a3:0000:0000:8a2e:0370:7334
IPv6 provides roughly 340 undecillion addresses (a number with 39 digits) — effectively unlimited. To keep them readable, leading zeros are dropped and one run of all-zero groups can be collapsed to ::, so the address above shortens to 2001:db8:85a3::8a2e:370:7334.
| IPv4 | IPv6 | |
|---|---|---|
| Size | 32-bit | 128-bit |
| Format | Decimal, dotted | Hexadecimal, colons |
| Example | 192.168.1.10 | 2001:db8::8a2e:370:7334 |
| Address space | ~4.3 billion | ~340 undecillion |
| Separator | . | : |
The world is mid-migration: most devices run both at once (called dual stack), which is why you’ll often see an IPv4 and an IPv6 address on the same machine.
Public vs private IP addresses
This trips up almost every beginner, so get it straight early: your device has two IPs that are both “yours” but serve different scopes.
- A private IP identifies your device inside your local network (home or office). It’s not reachable from the internet, and the same private addresses are reused on millions of networks worldwide.
- A public IP is assigned by your ISP and identifies your whole network to the internet. Every device behind your router shares it for outbound traffic.
Private addresses come from three reserved ranges (defined in RFC 1918) — memorize these, they’re a classic exam question:
| Class | Private range | Common use |
|---|---|---|
| A | 10.0.0.0 – 10.255.255.255 | Large networks |
| B | 172.16.0.0 – 172.31.255.255 | Medium networks |
| C | 192.168.0.0 – 192.168.255.255 | Home / small office |
That 192.168.x.x address on your laptop? Private. The address a website sees when you visit? Public. The thing that bridges the two is NAT.
NAT — how one public IP serves a whole house
Network Address Translation (NAT) is the trick that lets a dozen devices share a single public IP. Your router rewrites the private source address on outbound packets to its public address, remembers which device asked, and reverses the translation on the way back. It’s the main reason IPv4 didn’t collapse entirely when addresses ran out — and a core concept on Network+.
Static vs dynamic IP addresses
- Dynamic — assigned automatically and temporarily, and may change over time. This is the default for almost everything.
- Static — set manually and never changes. Used for devices that need a predictable address: servers, printers, routers, security cameras.
You rarely assign dynamic addresses by hand because a protocol does it for you.
DHCP — automatic addressing
Dynamic Host Configuration Protocol (DHCP) is the service (usually running on your router) that hands out IP addresses automatically when a device joins the network. In one exchange it also delivers the subnet mask, default gateway, and DNS server — everything the device needs to communicate. Without DHCP, you’d configure every phone and laptop by hand.
If a device set to DHCP can’t reach a server, Windows assigns itself an APIPA address in the 169.254.x.x range. Seeing a 169.254 address is a dead giveaway that DHCP failed — a troubleshooting signal worth memorizing.
Subnet masks and the default gateway
Two values always travel with an IP address:
- The subnet mask (e.g.
255.255.255.0) tells a device which part of its IP is the network and which part is the host — in other words, who’s “local” and who isn’t. If a destination is on the same network, the device talks to it directly; if not, it sends the traffic to the gateway. - The default gateway is the address of your router — the door to everything outside your local network. Traffic bound for the internet goes here first.
Modern networks express the mask compactly with CIDR notation: 192.168.1.10/24 means the first 24 bits are the network portion — equivalent to a 255.255.255.0 mask. Subnetting (slicing a network into smaller pieces) is a heavier topic and a big part of Network+ specifically.
DNS — names instead of numbers
Nobody wants to type 142.250.80.46 to reach Google. The Domain Name System (DNS) is the internet’s phone book: it translates human-friendly names like google.com into the IP addresses machines actually use. When a lookup is slow or failing, the symptom is “the internet is down” even though the connection is fine — a classic DNS troubleshooting scenario.
A few special addresses worth knowing
127.0.0.1— the loopback (or localhost). It always points back to your own device; pinging it tests whether your network software stack works at all.169.254.x.x— APIPA, the “DHCP failed” range mentioned above.255.255.255.255— the broadcast address, used to send to every device on a network at once.
How to find your IP address
On any machine, the command line tells you fast:
- Windows: open Command Prompt and run
ipconfig(oripconfig /allfor the full picture — IP, subnet mask, gateway, DNS). - macOS / Linux: run
ifconfigor the modernip a. - Your public IP: search “what is my IP” or visit a site like ipinfo.io — that’s the address the internet sees.
Running these yourself is exactly the kind of hands-on practice that makes networking stick. If you’re studying, do it inside a couple of virtual machines on a small virtual network — that’s lab #3 in my CompTIA A+ home lab.
The one-paragraph version
An IP address uniquely identifies a device on a network. IPv4 (192.168.1.10) is the common 32-bit format; IPv6 is the 128-bit successor built to never run out. Your device has a private IP on the local network and shares one public IP to the internet via NAT. DHCP hands out addresses automatically (a 169.254 address means it failed); the subnet mask defines what’s local and the default gateway is the way out; DNS turns names into numbers. Learn those eight terms and you understand the backbone of every network you’ll ever touch.