technitium v0.1.0

Networking

Technitium DNS Server — a full-featured, self-hosted, authoritative and recursive DNS server with ad-blocking, DNS-over-HTTPS/TLS, DHCP, and a clean web console. A powerful Pi-hole/NextDNS alternative that also hosts your own zones. Deployed as a host-networked Nomad service with a persistent config volume.

nomad-pack run technitium --registry nomploy

…or one line (add registry + run)

curl -fsSL https://packs.nomploy.com/install.sh | sh -s -- technitium

Needs nomad-pack on PATH. The script only adds the nomploy registry and runs this pack.

Source ↗ Project ↗ ★ 10k ⚑ Report an issue

1 task dns 53web 5380 1 volume image technitium/dns-server:latest tracks :latest image bumped today

Variables 10

values.hcl

Save as values.hcl, edit, then run:

nomad-pack run technitium -f values.hcl --registry nomploy

# The name of the Nomad job.
job_name = "technitium"

# The Nomad namespace to deploy into.
namespace = "default"

# The datacenters to deploy to.
datacenters = ["*"]

# The Technitium DNS Server image. Pin a tag in production.
image = "technitium/dns-server:latest"

# Host port for DNS queries (UDP + TCP), port 53.
dns_port = 53

# Host port for the web console (DNS_SERVER_WEB_SERVICE_HTTP_PORT).
web_port = 5380

# Web console admin password (DNS_SERVER_ADMIN_PASSWORD) for the 'admin' user. CHANGE THIS.
admin_password = "change-me-please"

# Named volume for Technitium config and zones (/etc/dns).
data_volume = "technitium_config"

# Placement constraints. Pin to the node holding the volume. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
constraints = []

# Resources for the Technitium task.
resources = {
    cpu    = 500
    memory = 256
  }

Name	Type	Default	Description
job_name	string	"technitium"	The name of the Nomad job.
namespace	string	"default"	The Nomad namespace to deploy into.
datacenters	list	["*"]	The datacenters to deploy to.
image	string	"technitium/dns-server:latest"	The Technitium DNS Server image. Pin a tag in production.
dns_port	number	53	Host port for DNS queries (UDP + TCP), port 53.
web_port	number	5380	Host port for the web console (DNS_SERVER_WEB_SERVICE_HTTP_PORT).
admin_password set me	string	"change-me-please"	Web console admin password (DNS_SERVER_ADMIN_PASSWORD) for the 'admin' user. CHANGE THIS.
data_volume	string	"technitium_config"	Named volume for Technitium config and zones (/etc/dns).
constraints	list	[]	Placement constraints. Pin to the node holding the volume. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
resources	object	{ cpu = 500 memory = 256 }	Resources for the Technitium task.

Back up this pack

This pack stores data in one Docker named volume: technitium_config

restic

# Run on the node hosting this pack. Point restic at your repo first:
#   export RESTIC_REPOSITORY="s3:https://<account>.r2.cloudflarestorage.com/<bucket>"
#   export RESTIC_PASSWORD="<repo-password>"
#   export AWS_ACCESS_KEY_ID=<key>  AWS_SECRET_ACCESS_KEY=<secret>
restic backup \
  /var/lib/docker/volumes/technitium_config/_data

rclone (sync to S3/R2)

rclone sync /var/lib/docker/volumes/technitium_config/_data backup:<bucket>/technitium_config

Paths assume the default Docker volume location (/var/lib/docker/volumes). Restore by stopping the job, restoring files into the same volume, and re-running the pack.

Readme

technitium

Technitium DNS Server — a full-featured, self-hosted DNS server. It works as an authoritative server for your own zones and a recursive/forwarding resolver, with network-wide ad-blocking, DNS-over-HTTPS/TLS/QUIC, an optional DHCP server, query logs, and a polished web console. A powerful Pi-hole / NextDNS alternative that can also host real DNS zones.

Single host-networked Nomad service with a persistent config volume.

Deploy

nomad-pack registry add nomploy https://github.com/Nomploy/nomad-packs
nomad-pack run technitium --registry=nomploy

Configure

Variable	Default	Description
`dns_port`	`53`	DNS query port (UDP + TCP).
`web_port`	`5380`	Web console port (`DNS_SERVER_WEB_SERVICE_HTTP_PORT`).
`admin_password`	`change-me-please`	Console admin password (`DNS_SERVER_ADMIN_PASSWORD`). Change it.
`data_volume`	`technitium_config`	`/etc/dns` — settings and zones.
`image`	`technitium/dns-server:latest`	Container image. Pin a tag in production.
`resources`	`{ cpu = 500, memory = 256 }`	Task resources.

Log in to the console as admin, set forwarders, enable ad-block lists, or add your own zones, then point clients' DNS at <node-ip>.

Port 53: binding it requires that nothing else on the node already listens there. On many Linux hosts you must first disable systemd-resolved's stub listener (DNSStubListener=no in /etc/systemd/resolved.conf). Pin the job to the node holding the volume with constraints.