0.3 Networking basics for cloud work
You can explain what happens between typing a URL and the page arriving.
Before:nothing requiredUnlocks:01. Cloud Foundations
Between typing a URL and a page arriving sits the whole of networking, and this topic walks that journey: IP addresses and CIDR notation, DNS resolution, TCP ports, TLS, and why distance costs milliseconds. It sits in the groundwork module because cloud networks are ordinary networks worn differently — subnets and route tables make no sense until this does. The persistent confusion is DNS propagation: changes feel slow because of caching and TTLs, not because updates crawl across the planet.
Work through these
IP addresses, subnets and CIDR notation
An address identifies a machine, a subnet groups addresses that sit together, and the slash notation is how the boundary between them is written. Every network you design in the cloud starts with drawing these ranges.
DNS: records, resolution, TTL and propagation myths
The naming system that turns a domain into an address, plus the caching that makes changes take time to appear everywhere. Understanding the caching is what dissolves most of the folklore about waiting for changes to spread.
TCP, ports, HTTP and HTTPS/TLS
The transport underneath the web: reliable connections, numbered ports, the request protocol on top and the encrypted version of it. This is the layer you will be opening and closing access to for the rest of the subject.
Latency, bandwidth and why distance costs milliseconds
Signals travel at a finite speed and every hop adds delay, which is why a server on the other side of the world feels slow no matter how fast it is. This is the physics behind every later decision about where to put things.
Sign in to keep your progress.
Free resources
Links last checked 29 Aug 2026.
Stuck here?
Ask a mentor. A real person answers, and they can see exactly which topic you're on. Usually within a couple of working days.
Checking your session…
Topics shown in module order.