I Built Private DNS Nodes on LXC for Pi‑hole and AdGuard Home ’Cause I Didn’t Want to Babysit a Raspberry Pi
Описание и применение
Создана управляемая служба приватных DNS‑узлов на LXC, использующая Pi‑hole или AdGuard Home с Unbound и автоматической генерацией DoT/DoH, позволяющая пользователям быстро развернуть защищённый DNS‑фильтр без обслуживания оборудования.
Задача
Running a private DNS filter requires maintaining hardware, patching, TLS termination, and ensuring compatibility across devices and networks.
Результат
The service delivers a fast, isolated DNS filtering node per customer, with encrypted DNS, DNSSEC, and optional fallback, while keeping resource usage low and allowing easy deletion.
Рабочий процесс
- Deploy a pre‑built LXC image on a cloud host (Netcup, Hetzner, OVH).
- Configure the container with the chosen filter (Pi‑hole or AdGuard Home).
- Unbound runs behind the filter for recursive resolution and DNSSEC validation.
- TLS termination for DoT/DoH is handled by a gateway that routes to the correct container.
- Generate hostname and certificate at deploy time.
- Provide optional fallback to upstream resolver if the node is unreachable.
- Delete the node to remove all data when no longer needed.
Доказательства
Each node is an LXC system container. If you haven’t used them: a container that behaves like a small Linux server (its own init, its own filesystem, its own processes and network) but shares the host’s kernel instead of booting a separate one.
Unbound behind it. Recursive resolving with DNSSEC validation, so no big public resolver sits in the middle.
DoT and DoH endpoints, generated for you.
Billing is prepaid and hourly, capped at $4/month. Delete the node whenever you like, and the data goes with it.
- Дата записи: 2026-10-25T10:11:35.556Z