charts

Technitium DNS Server Helm Chart

Version: 1.8.0 Type: application AppVersion: 14.3

Technitium DNS Server is a powerful and versatile DNS solution that can serve multiple purposes, from enhancing your network security by blocking ads and trackers (similar to Pi-hole or AdGuardHome) to acting as a robust authoritative DNS server for your domains. This Helm chart simplifies its deployment on Kubernetes, allowing you to leverage its advanced features with ease.

Features

Maintainers

Name Email Url
obeone obeone@obeone.org  

Source Code

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 See the docs 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. This typically includes storage for DNS configurations and logs.
service object See values.yaml Configures service settings for the chart, including various ports for DNS, DoT, DoH, and DHCP. Depending on your Kubernetes version, you may or may not be able to mix UDP and TCP services.

Usage Examples

Basic Deployment

To deploy Technitium DNS Server with default settings:

helm install technitium-dnsserver technitium-dnsserver/

Enabling Ad-blocking

To enable ad-blocking, you might need to configure specific environment variables or mount a custom configuration. Refer to the official Technitium DNS Server documentation for detailed ad-blocking setup.

Exposing the Web Interface via Ingress

To access the web interface through an Ingress controller, you can configure the ingress.main section in your values.yaml:

ingress:
  main:
    enabled: true
    hosts:
      - host: dns.yourdomain.com
        paths:
          - path: /
            pathType: Prefix
    tls:
      - hosts:
          - dns.yourdomain.com
        secretName: dns-tls-secret

Autogenerated from chart metadata using helm-docs v1.14.2