TTEL Fieldnotes
Technology / Networks / Infrastructure

A closer look
at connection.

Every page load crosses a remarkable system of names, routes and agreements. These fieldnotes unpack the infrastructure we use every day.

Explore the fieldnotes ↗

Three layers worth knowing.

Fieldnotes / 001–003
001 — NAMING

Names are not addresses.

DNS maps a hostname to records, often including IPv4 or IPv6 addresses. A recursive resolver follows referrals and caches answers for their time to live.

Changing a record does not instantly replace cached answers everywhere. That is why a DNS change can appear to work on one network before another.

Read the DNS foundations ↗
002 — ROUTING

The path is a negotiation.

The internet is a network of independently operated networks. BGP lets them exchange reachability information and apply policies about which routes to use.

A chosen route is not necessarily the shortest geographic path. Commercial relationships, filtering and network policy also shape where packets travel.

Explore BGP-4 ↗
003 — ENCRYPTION

Trust has boundaries.

TLS protects data in transit between its endpoints. A browser checks a server certificate and negotiates cryptographic keys before exchanging application data.

HTTPS does not establish that a page is truthful. It protects the connection to the named endpoint; the destination still receives what you send.

Look inside TLS 1.3 ↗