Being writtenNetwork & voice

Network fundamentals for IT support

Addressing, DNS, DHCP and NAT — and a method for finding which of them is broken.

LevelFoundation
Material3 modules, 10 lessons
Reading time1 h 58 m
StatusBeing written — not open

This course is not available yet

It is being written. The outline below is what it will cover, and it is unlikely to change much. There is no enrolment and no date — when it is ready it will be on this page. Several of the lessons are built around tools on this site that already work, so you can practise the measurements today.

If you need this capability now rather than later, Managed network operations is the service that covers it, or talk to us.

Who it is for

First- and second-line support staff who can follow a runbook and would like to know why it works.

Foundation. No prior experience assumed. Written for people whose job is not IT.

No prerequisites. Nothing is assumed beyond using a computer at work.

What you will be able to do

  • Read an IP address and subnet mask and say what is local and what is not
  • Split a network into subnets of the right size, and explain why the order of allocation matters
  • Trace a name-resolution failure from the client to the authoritative nameserver
  • Tell a DNS problem, a routing problem and an application problem apart from the symptoms

Outline

3 modules, 10 lessons, 1 h 58 m of material. The times are the sum of the lessons rather than a round figure.

01Addressing

The arithmetic, and what it tells you about where a packet can and cannot go.

Addresses, masks and prefixes12 m

What the mask is for, and reading a prefix length without converting to binary.

Subnetting, and sizing it right14 m

Splitting a block, and why allocating largest-first avoids stranding the space.

Private, public and carrier NAT10 m

The reserved ranges, and why an address beginning 100.64 cannot accept an inbound connection.

IPv6, briefly and without fear12 m

What is genuinely different, and what is the same with longer numbers.

02Names

Most things reported as "the network is down" are name resolution.

How a lookup actually happens12 m

Stub resolver, recursive resolver, authoritative nameserver, and the caches between them.

Records worth knowing12 m

A, AAAA, CNAME, MX, TXT, SRV, PTR — and the CNAME rule people break.

TTLs and why a change has not taken effect10 m

Caching, negative caching, and planning a cutover around both.

03Finding the fault

A method, so the answer does not depend on which layer you happened to guess.

Working up from the wire12 m

Link, address, gateway, name, route, application — in that order, every time.

What a traceroute does and does not tell you12 m

Why a hop that does not reply is almost never the fault.

MTU, fragmentation and the sites that half-load12 m

The symptom that looks like nothing else, and how to confirm it.

Format. Written lessons with exercises you can work through using this site’s subnet calculator and DNS tools. Delivery mechanism is not built yet.

Would you rather we just did it?

This course exists because the work behind it is work we do. If you need the result rather than the skill, managed network operations is the service that covers it.