If you're going to understand networking, these three ideas are the foundation everything else sits on. Get comfortable with these before moving on to anything more advanced — VLANs, routing, firewalls — because all of it assumes you already have this down.
What an IP address actually is
An IP address is just a way to identify a device on a network, the same way a street address identifies a building. IPv4 addresses — still the most common type you'll work with day to day — are written as four numbers separated by dots, like 192.168.1.15, where each number can range from 0 to 255.
Every device that wants to communicate on a network needs one, and no two devices on the same network can have the same address at the same time — that's called an IP conflict, and it's a real troubleshooting scenario you'll run into.
Public vs. private addresses
Private IP ranges are reserved for use inside internal networks and aren't routable on the public internet. If you see an address in one of these ranges, you're looking at internal network traffic:
- 10.0.0.0 – 10.255.255.255
- 172.16.0.0 – 172.31.255.255
- 192.168.0.0 – 192.168.255.255
Subnets: dividing a network into manageable pieces
A subnet mask determines which part of an IP address identifies the network and which part identifies the specific device. You'll usually see this written in CIDR notation, like 192.168.1.0/24 — the "/24" means the first 24 bits are the network portion, leaving the last 8 bits (256 possible addresses, 254 usable) for individual devices.
Subnetting exists because putting every device on one giant flat network doesn't scale — it creates unnecessary broadcast traffic and makes it harder to control who can talk to what. Breaking a network into smaller subnets is one of the first things that separates a home network setup from a professionally managed one.
DNS: the internet's phone book
Nobody memorizes IP addresses to visit a website — you type a name like "example.com" and expect it to work. DNS (Domain Name System) is the service that translates that human-readable name into the actual IP address the device needs to make a connection.
When you type a web address, your device asks a DNS server "what's the IP address for this name?" The DNS server responds, and only then does your device actually connect to that IP address. If DNS is broken, the internet connection itself might be completely fine — but nothing will resolve, which is why "the internet's down" is very often actually a DNS problem in disguise.
Quick reference: commands worth knowing
- ipconfig (Windows) / ifconfig or ip addr (Mac/Linux) — shows your device's current IP configuration
- ping [address] — tests basic connectivity to another device or server
- nslookup [domain] — manually checks what IP address a domain name resolves to
- tracert (Windows) / traceroute (Mac/Linux) — shows the path traffic takes to reach a destination, useful for finding where a connection is failing
Once these three concepts click, most other networking topics start making a lot more sense — because nearly everything else in networking is really just a more specific application of "how do devices find and talk to each other."