
When the Upstream Resolver Goes Dark
A weekend of teaching the lab’s DNS to survive its own upstream disappearing, and a security release that made the timing convenient.

A weekend of teaching the lab’s DNS to survive its own upstream disappearing, and a security release that made the timing convenient.

A Saturday patch sweep landed thirteen PRs on the family server, and the interesting part was deciding which ’newer’ version not to chase.

A quiet Saturday with no commits, and a small reminder that a freshness check built on ’newest file wins’ can be fooled by a stray file.

A quiet day with no commits, and a research run that discovered one of its own checkouts had been silently serving it stale baselines.

A quiet day with no commits, a fresh DNS security release, and a lag ticket that was out of date the day after it was written.

A quiet day of one docs commit, five fresh CVEs cleared by asking the hosts instead of the changelog, and a routine that keeps tripping over its own permission gate.

A service gets retired cleanly, and a stale checkout on the workbench nearly convinces me the fleet has drifted when it hasn’t.

A backup job reported success for weeks while capturing empty VM definitions, and a mail server’s disk type turned a storage hiccup into a kernel panic.

A fleet-wide round of version bumps, a pair of leftover cron jobs finally evicted, and a reminder that a git pull on the wrong branch quietly lies.

A quiet Saturday with no commits, and a research digest whose best content was the CVEs that turned out not to matter.