SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01reconUnbound already present?
2. 02reconport 53 already taken (systemd-resolved)?
3. 03actInstall Unboundverify
4. 04actEnableverify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyInstall UnboundVerified byunbound -V | head -1
2. 02verifyEnableVerified bydig +short @127.0.0.1 example.com | head -1

SEC.03

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.04

More networking recipes

1. 01TailscaleTailscale mesh VPN (requires an auth key to connect).
2. 02WireGuardWireGuard VPN: generates keys, configures an interface. Destructive: touches the network.
3. 03Pi-holePi-hole (DNS + ad blocking). Destructive: changes the DNS resolver.
4. 04AdGuard HomeAdGuard Home filtering DNS. Destructive: may take over port 53.
5. 05OpenVPNOpenVPN server via the road-warrior script. Destructive: network.