github paimonsoror/telltaledns v0.1.0
TelltaleDNS 0.1.0

latest releases: edge, v0.7.0, v0.6.0...
one month ago

The first stable release of TelltaleDNS: a filtering, encrypted, observable DNS resolver that runs on a Raspberry Pi, in Kubernetes, or on both as one cluster.

Highlights

  • Fast and small. Every CPU core answers on its own, with no garbage-collection pauses; cache hits take about 150 ns. About 60 MB of memory on a Pi 4 with 2.7 million blocked names.
  • Blocking you can explain. Hosts files, AdBlock-style lists, and regexes are compiled in the background into one compact snapshot. Every blocked answer says which list and line decided it, in the query log, the API, and telltale explain.
  • Groups for your networks. Each VLAN or set of devices gets its own lists, blocked services, safe search, schedules, rewrites, DNS64, and upstream servers. Every chart and log line shows which group a question came from.
  • Encrypted both ways. DoT, DoH (HTTP/2 and HTTP/3), and DoQ for your devices; DoT, DoH, DoQ, DNSCrypt, and DNS stamps to upstreams; DNSSEC validation, aggressive NSEC (RFC 8198), or full recursion from the root.
  • Observable. Per-question timing and percentiles, a searchable columnar query log, a live view across the cluster, Prometheus metrics with a Grafana dashboard, device anomaly detection, alerts (email, ntfy, Gotify, Slack, webhooks), and exports to syslog, OpenTelemetry, and dnstap.
  • One cluster, one place to manage it. A Pi and Kubernetes nodes form one cluster with replicated configuration, write forwarding, automatic failover, and configuration from Git.
  • Ready for AI agents. Scoped agent tokens or SSO, an MCP server whose changes come as plans you approve, and vqlog for analytics in one line.
  • Easy to try. Brings over a Pi-hole or Technitium setup; installs as a container, a Helm chart, or a native systemd service with a guided installer (and --uninstall).

Install

  • Container: ghcr.io/paimonsoror/telltale:0.1.0 (also :0.1, :0, :latest) for amd64, arm64, and arm/v7.
  • Kubernetes: helm install telltale oci://ghcr.io/paimonsoror/charts/telltale --version 0.1.0
  • Raspberry Pi or Linux: curl -fsSLO https://raw.githubusercontent.com/paimonsoror/telltaledns/v0.1.0/deploy/systemd/install.sh && sudo sh install.sh

Binaries are signed: SHA256SUMS.minisig verifies with the key in deploy/release/telltale-release.pub, and install.sh and telltale self-update check it for you.

Upgrading from edge builds

Nothing to change in your configuration. Native installs on the edge channel can stay there (telltale self-update --channel edge) or move to stable (telltale self-update). Container and Helm users can switch from :edge to a version tag.

Documentation: https://paimonsoror.github.io/telltaledns/ · Every design decision: https://paimonsoror.github.io/telltaledns/decisions.html

Full Changelog: https://github.com/paimonsoror/telltaledns/commits/v0.1.0

Don't miss a new telltaledns release

NewReleases is sending notifications on new releases.