Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

I Built Private DNS Nodes on LXC for Pi‑hole and AdGuard Home ’Cause I Didn’t Want to Babysit a Raspberry Pi

说明与用途

在 LXC 上构建的托管私有 DNS 节点,使用 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