Self-host Technitium DNS Server with Levelrail
A full-featured authoritative and recursive DNS server with DNS-over-HTTPS/TLS and a web console.
- AuthorTechnitiumSoftware
- LicenceGPL-3.0
- Memory256 MiB
- Archarm64
- Services1
How to self-host Technitium DNS Server
-
Pull the images
One image is pulled on your server.
Show images
technitium/dns-server:15.5.1
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 5380.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Technitium DNS Server requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 5380
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 5380 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Technitium DNS Server. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Technitium DNS Server docs page.
Deploy Technitium DNS Server your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Technitium DNS Server from the CLI
levelrail-cli templates deploy technitium-dns --name my-technitium-dns Deploy Technitium DNS Server with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/technitium-dns/deploy Technitium DNS Server configuration
Technitium DNS Server services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| technitium-dns | technitium/dns-server:15.5.1 | 5380 | technitium_config -> /etc/dns |
Technitium DNS Server environment variables
| Variable | Service | Value |
|---|---|---|
| DNS_SERVER_ADMIN_PASSWORD | technitium-dns | Generated at deploy |
| DNS_SERVER_DOMAIN | technitium-dns | Preset by the template |
Ports and volumes
- Ports
- 5380
- Volumes
- 1 named mount: technitium_config -> /etc/dns
Technitium DNS Server FAQ
How much memory does Technitium DNS Server need?
The catalog lists about 256 MiB of memory for Technitium DNS Server.
Does Technitium DNS Server run on arm64?
For Technitium DNS Server, an arm64 image is published; amd64 is image published.
What licence is Technitium DNS Server under?
Technitium DNS Server is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Technitium DNS Server need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Technitium DNS Server use?
Technitium DNS Server listens on port 5380 inside the stack.
Where does Technitium DNS Server keep its data?
In a named volume: technitium_config mounted at /etc/dns.
Can I deploy Technitium DNS Server on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Technitium DNS Server, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image technitium/dns-server:15.5.1 is what you deploy there.