charts

technitium-dnsserver

Technitium DNS Server is a DNS that can be use as a piHole or AdGuardHome replacement. It can also be used as authoritative server

TL;DR

helm repo add obeone https://charts.obeone.cloud
helm repo update
helm install technitium-dnsserver obeone/technitium-dnsserver

About

Technitium DNS Server is a full-featured, self-hosted DNS server with a web console. It works both as a recursive resolver with ad and tracker blocking (a Pi-hole or AdGuard Home replacement) and as an authoritative server for your own zones, with DNS-over-HTTPS and DNS-over-TLS support built in.

Application: technitium.com/dns
Container image: technitium/dns-server
Source code: github.com/TechnitiumSoftware/DnsServer
Chart source: charts/technitium-dnsserver

Prerequisites

Helm 3
A Kubernetes cluster matching the chart’s kubeVersion constraint (see Chart.yaml)

Configuration

This chart is built on the k8s-at-home common library (v4). Most configuration keys (image, env, service, ingress, persistence, …) follow its schema, so the library supports more than what is spelled out in values.yaml.

Defaults are meant to work out of the box on any cluster. The full list of options lives in values.yaml, is validated by values.schema.json at install time, and is documented in the Values section below. Override it with your own values file:

helm install technitium-dnsserver obeone/technitium-dnsserver -f my-values.yaml

Exposing DNS

The default Service publishes the web console (HTTP/HTTPS) together with DNS on port 53 over both TCP and UDP; DHCP and DNS-over-TLS ports are defined too. Adapt service in values.yaml to what your load balancer supports.

Upgrading

helm repo update
helm upgrade technitium-dnsserver obeone/technitium-dnsserver

Each release lists its changes in the Artifact Hub changelog; give it a look before jumping across several chart versions.

Uninstalling

helm uninstall technitium-dnsserver

PersistentVolumeClaims created by the chart are kept around: delete them manually if you also want the data gone.

Requirements

Repository	Name	Version
https://library-charts.k8s-at-home.com	common	4.5.2

Values

Key	Type	Default	Description
env	object	See below	Environment variables for the container. Refer to Technitium DNS Server documentation for available variables.
env.TZ	string	`"UTC"`	Set the container timezone
image.pullPolicy	string	`"Always"`	image pull policy
image.repository	string	`"technitium/dns-server"`	image repository
image.tag	string	chart.appVersion	image tag
ingress.main	object	`{"annotations":{},"enabled":false,"hosts":[{"host":"my.host.local","paths":[{"path":"/","pathType":"Prefix"}]}],"ingressClassName":"","tls":[{"hosts":["my.host.local"],"secretName":"mycert-tls"}]}`	Enable and configure ingress settings for the chart. For more details, see the common library chart documentation.
persistence	object	See values.yaml	Configure persistence settings for the chart.
service	object	See values.yaml	Configures service settings for the chart. Depending on your Kubernetes version, you may or may not be able to mix UDP and TCP services.
service.main.ports.dhcp	object	`{"enabled":true,"port":67,"protocol":"UDP"}`	UDP port for DHCP services
service.main.ports.dns-tcp	object	`{"enabled":true,"port":53,"protocol":"TCP"}`	TCP port for standard DNS queries and zone transfers
service.main.ports.dns-udp	object	`{"enabled":true,"port":53,"protocol":"UDP"}`	UDP port for standard DNS queries
service.main.ports.doh-reverse	object	`{"enabled":true,"port":8053,"protocol":"TCP"}`	TCP port for DNS-over-HTTPS (DoH) reverse proxy
service.main.ports.dot	object	`{"enabled":true,"port":853,"protocol":"TCP"}`	TCP port for DNS-over-TLS (DoT)
service.main.ports.http	object	`{"enabled":true,"port":80,"protocol":"TCP","targetPort":5380}`	HTTP port for the web interface
service.main.ports.https	object	`{"enabled":true,"port":443,"targetPort":53443}`	HTTPS port for the web interface

Verifying the chart signature

Charts in this repository are signed with GPG and every release ships a provenance file. The public key is available at charts.obeone.cloud/public_key.gpg, fingerprint B9FE852F28888D27F8C9A11CD33E04CD22E335CE.

# Import the signing key into a legacy keyring (helm verifies with GnuPG v1 keyrings)
curl -fsSL https://charts.obeone.cloud/public_key.gpg | gpg --import
gpg --export > ~/.gnupg/pubring.gpg

# Pull the chart and check it against its provenance file
helm pull --verify obeone/technitium-dnsserver

Support

This is a personal chart repository, maintained on a best-effort basis. Bug reports and contributions are welcome on GitHub.

Autogenerated from chart metadata using helm-docs v1.14.2