# Self-host Technitium DNS Server

> A full-featured authoritative and recursive DNS server with DNS-over-HTTPS/TLS and a web console.

- Page: https://levelrail.com/templates/technitium-dns/
- JSON: https://levelrail.com/templates/technitium-dns.json
- Category: Infrastructure
- Licence: GPL-3.0 (Copyleft license)
- Source: https://github.com/TechnitiumSoftware/DnsServer
- Upstream docs: https://technitium.com/dns/

## Requirements
- Memory: about 256 MiB
- amd64: published, arm64: published
- Needs configuration before start: no
- Pinned image tag: 15.5.1

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| technitium-dns | technitium/dns-server | 15.5.1 | 5380 | technitium_config -> /etc/dns |

## Environment

| Service | Variable | Kind |
| --- | --- | --- |
| technitium-dns | DNS_SERVER_ADMIN_PASSWORD | generated |
| technitium-dns | DNS_SERVER_DOMAIN | preset |

## Deploy

### CLI

```bash
levelrail-cli templates deploy technitium-dns --name my-technitium-dns
```

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/technitium-dns/deploy
```

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

## Questions

### 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.

Self-host Technitium DNS Server, Technitium DNS Server docker compose file, deploy Technitium DNS Server on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
