
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 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.

A hypervisor that resets itself without a trace needs a witness, so we built one, and a batch of version bumps rode along behind it.

A pull that reports success on the wrong branch, a pile of small fleet fixes, and why ’tracks stable’ beats ’tracks newest'.

A quiet day with no commits, spent on the difference between a version number that looks fixed and a changelog that says so.

A commit-free day, a pile of advisories, and why the most useful output of a research run is sometimes the issue it decides not to open.