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.
- 01reconUnbound already present?
- 02reconservice active? existing config (interfaces, ACLs) to preserve?
- 03reconwho holds port 53 and where (systemd-resolved on 127.0.0.53 is fine; 0.0.0.0 or 127.0.0.1 is not)
- 04reconcurrent server resolver (unchanged by this recipe)
- 05recondistro and package manager
- 06actInstall Unboundverify
- 07actValidate the configurationverify
- 08actEnableverify
- 09actVerify DNSSEC validationverify
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.
- 01verifyInstall UnboundVerified by
unbound -V | head -1 - 02verifyValidate the configurationVerified by
unbound-checkconf - 03verifyEnableVerified by
systemctl is-active unbound && dig +short +time=3 @127.0.0.1 example.com | head -1 - 04verifyVerify DNSSEC validationVerified by
dig +dnssec +time=3 @127.0.0.1 cloudflare.com | grep -cE 'flags:.* ad[; ]'
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never break the server connectivity: no change to the default route, /etc/resolv.conf or the rules that let the Servor agent and the SSH session out. Compare the default route and DNS resolution before/after. Do not change the server resolver (resolv.conf, systemd-resolved) unless explicitly asked, and then only after a successful dig against Unbound. Never listen on 0.0.0.0 and keep access-control limited to localhost or trusted networks: no open resolver. Do not overwrite an existing Unbound config.
SEC.04
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.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.05
Deploy on Servor button
Maintain DNS resolver (Unbound) or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.
Dark background
Light background[](https://servor.app/deploy/install-unbound)SEC.06
More networking recipes
- 01TailscaleTailscale mesh VPN: auth key or login link, without touching the server DNS.
- 02WireGuardWireGuard VPN server + a first client, without touching routing. Destructive: network interface.
- 03Pi-holePi-hole v6 (DNS + ad blocking) in a container, on the chosen IP. Destructive when listening on 0.0.0.0 (port 53).
- 04AdGuard HomeAdGuard Home filtering DNS, local UI. Destructive: may free port 53.
- 05OpenVPNOpenVPN server via the road-warrior script (angristan), first client created. Destructive: network.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.