OWOpen Web Notes
Browse the notebook

Archive

Recent entries, kept in a simple chronological list.

  1. Authoritative DNS comes first
    When a record changes, check the authoritative server before recursive caches. It separates a publishing problem from ordinary propagation delay.
  2. A health check should stay boring
    A small local endpoint with no database or external requests tells you whether the web process and route are alive without creating new failure modes.
  3. Test transfers, not only handshakes
    Opening a socket proves very little about a route. A measured file transfer catches stalls and resets that appear after the first packets.
  4. Keep recovery notes beside the service
    A concise record of listeners, certificates and validation commands makes routine maintenance safer when the original operator is unavailable.