-
Active, and refusing every query
A routine change to add a forwarding rule took DNS down for the entire lab. Every query from every machine, internal names and external ones alike, came back REFUSED from both resolvers.
-
The alert fired six times and the test said it did not
A new alert had just been added to catch a server simply dying. Proving it meant inducing the failure: stop the thing that reports the machine is alive, wait, and confirm the alert fires and the notification arrives.
-
Forty-three checks passed with a key that did not exist
A test suite for the DNS resolvers had a weakness worth closing: if the SSH key it used went missing, every check would fail, and thirty-seven DNS failures would be reported for what was actually one authentication problem.
-
Status: the lab stops being one machine
The second physical server is online. For the first time this project is not one computer with a lot of ambition attached to it.
-
The off-by-one that answered
A planned feature of this lab lets you text a question to it and get an answer back, so that basic status is reachable when the internet is not. One of the questions is how full a machine’s disks are.
-
Exit 3 means either
A new test suite reported a problem on two healthy gateways. The lab’s monitoring notes said drift was zero on both machines. One of the two had to be wrong, and finding out which produced a defect worth more than the answer.
-
Why CrowdSec
Anything with a public address is attacked continuously, within minutes of existing, by software that is not interested in what it found. The rented gateways in this lab carry that traffic all day.
-
Why Headscale
The machines in this lab are not all in the same place. Some are virtual machines at home, some are servers rented in other countries, and some are the devices people actually carry: laptops, phones and tablets, moving between home networks, mobile data and whatever…
-
Why Unbound
Every connection to anything starts with a name being turned into an address. In this lab that translation is done by two machines the lab owns, running Unbound, rather than by the internet provider’s resolver or by whatever the router was shipped with.