Before you start
Nothing required — this is genuinely foundational networking.
CLUSTER 0.3
Every device on a network needs two things before it can do anything: an address, and a way to find other addresses by name instead of memorising numbers. DNS and DHCP quietly handle both, for every device, every time.
Drag to rotate · click a node to jump to that topic
Think of it as: the phonebook of the internet
You type "google.com"; DNS translates that into the actual numeric address (an IP address) computers use to find each other. Without it, you'd need to memorise numbers instead of names for every website and internal server.
Think of it as: the receptionist handing out visitor badges
When a device joins a network, it needs an IP address to communicate. DHCP hands one out automatically — no one manually types in network settings on every laptop, phone, and printer in a building.
Think of it as: DNS's internal, private cousin
Companies run their own internal DNS for private resources — a file server called "FILES01" that the public internet has never heard of, but every laptop on the corporate network can find instantly.
Think of it as: the first two questions any IT person asks
"Can you reach the internet at all?" and "can your computer resolve names?" are the first two checks in almost any network problem — because DNS and DHCP failures are two of the most common root causes of "the internet is down."
"The Wi-Fi isn't working" is very often actually "DHCP didn't hand out an address" or "DNS can't resolve names" — the connection itself is fine, but one of these two invisible services quietly failed. Recognising the difference is most of the job in early-stage IT support.
REAL-WORLD SCENARIO
An employee's laptop shows "no internet" after a Monday morning restart. IT checks and finds it never got an IP address from DHCP — the service had a temporary outage over the weekend. Once DHCP is back up, the laptop requests an address automatically and reconnects with zero further action from the user.