Field notes for dependable systems

Find the signal in infrastructure noise.

Northstar Docs is a compact, vendor-neutral reference for the layers that make a website reachable: DNS, TCP, TLS, HTTP, and the server behind them.

Core topics

A small map of the web stack

Each guide focuses on observable behavior, useful checks, and the boundary between one layer and the next.

DNS without guesswork

Follow a name from resolver to authoritative answer and separate stale caches from incorrect records.

  • Records
  • TTL
  • Resolvers

Read a TLS failure

Understand certificates, names, negotiation, and why a successful TCP connection can still fail securely.

  • SNI
  • ALPN
  • Certificates

Status codes as evidence

Use response codes, headers, and timing to identify which component actually handled a request.

  • Headers
  • Caching
  • Errors

A repeatable method

Observe before you change.

Most outages become harder when several layers are changed at once. A calmer approach is to state the expected path, test one boundary, and keep the last known-good state close.

  1. Describe the expected path.Name every hop from the client to the application.
  2. Choose one boundary.Test whether traffic crosses it in both directions.
  3. Record the evidence.Keep timestamps, status codes, and the exact command or request.
  4. Change one variable.Retest the same boundary and compare the result.

Quick reference

Need a clean starting point?

Use the request-path checklist to turn “the site is down” into a specific, testable statement.

Open the checklist