Independent by design.PURE GO / v0.8.44

A recursive DNS resolver. Entirely yours.

Every query.
A clear path.

From the root to the answer. Labyrinth resolves, validates and protects your DNS — in one small binary you control.

One command. Then you’re in.
curl -sSL https://labyrinthdns.com/install.sh | bash

Linux & macOS · run as root · includes setup wizard

01 / Zero dependencies02 / Self-hosted03 / MIT licensed
THE RESOLUTION LABYRINTHFIG. 001
example.com
ROOT / ENTRYANSWER / EXIT
NOERROR93.184.216.34
Root → TLD → Authoritative → YouIllustrated query
FOLLOW THE THREAD Built for the curious. Made for the network.
6.8 MB

Single binary

22M/s

Cache reads

45 ns

Cache get

1.4 µs

Cached resolve

256

Cache shards

40+

RFCs implemented

Benchmarked on AMD Ryzen 9 9950X3D · labyrinth-bench · single thread

01 · Features

Small footprint.
Nothing left out.

The resolver, the protection, the visibility. Everything ships together — no plugins to assemble or services to babysit.

labyrinth / executable
6.8 MBOne file. Every layer.
RESOLVE / VALIDATE / OBSERVE
/01

Single binary

Resolver, dashboard, auth and blocklist engine in one 6.8 MB executable. No runtime dependencies, no cgo, no installer roulette.

/02

Web dashboard

Real-time monitoring, live query stream, cache management and report exports. Dark and light theme, on 127.0.0.1:9153.

/03

DNSSEC validation

Full chain from the root KSK — RSA, ECDSA P-256/P-384, Ed25519 — with aggressive NSEC/NSEC3 synthesis (RFC 8198).

/04

DNS blocklist

Pi-hole style blocking with hosts, domain and AdBlock Plus list formats, auto-refreshed on a schedule you set.

/05

Encrypted transports

DoT on :853, DoH and DoH3 on the web endpoint, EDNS padding on encrypted transports. One flag each in labyrinth.yaml.

UDP :53TCP :53DoT :853DoHDoH3
/06

Hardened

Bailiwick enforcement (RFC 5452), rate limiting, response rate limiting, and NSEC3 hash budgets that close CVE-2023-50387 / 50868.

/07

Observable

Prometheus metrics, a native Zabbix agent, structured JSON logs and a WebSocket query stream — with RFC-compliance counters.

/08

Self-updating

Version check and one-click update from the dashboard. Read-only installs update at the host level.

02 · Dashboard

Your network.
In plain sight.

See what’s resolving, what’s cached and what’s blocked. A live query stream and a built-in dashboard, without another service to deploy. Explore the preview below.

labyrinth — 127.0.0.1:9153

A window into your resolver

Every answer has a story.

INTERACTIVE PREVIEW

Queries / min

1,240

Cache hit ratio

87%

Blocked today

1,204

Upstream p50

12 ms

ws · live queries
5 shown
QueryTime · Status
github.comA34 msNOERROR
cdn.jsdelivr.netAAAA8 msCACHE
ads.tracker.netA1 msBLOCKED
api.githubusercontent.comA51 msNOERROR
registry.npmjs.orgA12 msCACHE

A redrawn impression of the built-in dashboard — illustrative numbers, real layout.

03 · Interactive

Follow a query through the labyrinth.

No mystery upstream. Watch a lookup travel through the root, TLD and authoritative servers, then return with a validated answer. Press play or drag the nodes to explore.

Mini Map
ready — press play
00 / 11 steps~1.4 µs cached · 34 ms cold

waiting for the first query…

Drawn with @xyflow/react · the trace is illustrative, the pipeline is real.

Also in the DNS toolbox

NothingDNS

Less noise.
More network.

YOUR INFRASTRUCTURE. YOUR RULES.

Looking for authoritative DNS, too?

Labyrinth focuses on recursive resolution. NothingDNS takes on the wider DNS stack: serve your own zones, resolve queries and shape traffic policies in a self-contained, open-source Go binary.

  • Authoritative & recursive DNS
  • Zone management & clustering
  • Blocklists & response policies
Explore NothingDNS

Self-hosted · MIT licensed · nothingdns.com

04 · Performance

Benchmarked, not bragged.

Numbers from labyrinth-bench on a single AMD Ryzen 9 9950X3D thread. Run the same benchmark yourself — it ships with every release.

  • 256-shard cache

    Lock-striped shards keep reads parallel across cores — 22M cache reads per second without contention.

  • Request coalescing

    Identical in-flight queries share a single upstream flight instead of stampeding the authoritative servers.

  • Fast by default

    QNAME minimisation and DNSSEC validation on out of the box, with cache TTLs you can tune live from the dashboard.

OperationThroughput · latency
Cache get22M ops/s · 45 ns
Name decode22.6M ops/s · 44 ns
Cache set19M ops/s · 53 ns
Wire unpack4.4M ops/s · 225 ns
Wire pack2.6M ops/s · 391 ns
FNV-1a hash331M ops/s · 3 ns
Full resolve (cached)700K ops/s · 1.4 µs

AMD Ryzen 9 9950X3D · labyrinth-bench · single thread · cache-entry latencies in ns, resolve in µs

05 · Standards

Forty-some RFCs, pinned by tests.

About 45 standards across nine capability groups. Each row is backed by a behavioural pin test under the rfcNNNN_*_test.go convention — a regression fails the suite instead of silently degrading the resolver.

RFC 1034 / 1035Domain names — concepts + implementationFull
RFC 1034 §3.7AA bit clear on resolver responsesPinned
RFC 1035 §2.3.4Label and name length caps (63 / 255)Pinned
RFC 2181DNS clarificationsFull
RFC 2308 §5Negative cache TTL = MIN(SOA TTL, SOA.MINIMUM)Pinned
RFC 3596AAAA recordsFull
RFC 3597Handling unknown RR typesFull
RFC 5452 §3In-bailiwick sanitisationPinned
RFC 5452 §6DNS 0x20 case randomisationPinned
RFC 6604 / 6672xNAME RCODE + DNAME redirectionFull
RFC 9156QNAME minimisationFull
RFC 9460SVCB / HTTPS resource recordsFull

Full matrix with per-entry IETF datatracker links lives on the dashboard’s About page.

06 · Positioning

Your network. Your rules.

Labyrinth is ideal when you want a self-contained recursive resolver without the operational complexity. Here is how that trade looks next to the usual alternatives.

CapabilityLabyrinthThis oneClassic resolversPublic resolvers
SetupOne binary + setup wizardPackages + hand-edited configNothing to run
ManagementBuilt-in dashboardConfig files and CLIsVendor web console
MetricsPrometheus + Zabbix nativeExporters and pluginsNot yours to read
BlocklistsBuilt-in, Pi-hole styleRPZ zones or extra layersUp to the vendor
Encrypted DNSDoT · DoH · DoH3 built inVaries — modules or proxiesYes — to them
Your queriesStay on your boxStay on your boxSomeone else's business

The honest pitch: the control of running your own resolver, without the weekend of YAML. Capabilities vary by resolver and version — compare against your own setup.

Before the first query

A few good
questions.

The practical details that help you decide if Labyrinth belongs on your network.

01Where do my queries go?

Labyrinth runs on your own machine and resolves names by asking root, TLD and authoritative servers. You control the resolver and its logs. Encrypted client transports protect the connection to your resolver; they don’t make every upstream query private.

Understand resolution
02Can I host my own DNS zones?

Labyrinth is a recursive resolver. If you also need authoritative DNS, zone management and clustering, take a look at NothingDNS.

Explore NothingDNS
03How do I get to the dashboard?

After installation, open http://127.0.0.1:9153 on the host to complete setup. The dashboard binds to localhost by default. Configure authentication and TLS before exposing it to your network.

Dashboard guide
04Can I reproduce the benchmark numbers?

Yes. Releases include labyrinth-bench. The numbers above are single-thread microbenchmarks on an AMD Ryzen 9 9950X3D. Actual DNS response times also depend on the network, cache state and upstream servers.

Run the benchmarks

07 · Install

Up and running in one line.

Choose the method that fits your environment. Zero-config start with sane defaults, an interactive setup wizard on first run, and everything configurable from labyrinth.yaml.

one-line install (Linux/macOS, as root)
curl -sSL https://labyrinthdns.com/install.sh | bash
installer flags
# Pin a specific release
curl -sSL https://labyrinthdns.com/install.sh | \
  bash -s -- --version v0.8.44

# Install without the systemd service
curl -sSL https://labyrinthdns.com/install.sh | \
  bash -s -- --no-service

Downloads the latest release to /opt/labyrinth/bin, installs a default config, sets up a systemd service and starts Labyrinth. Then open http://127.0.0.1:9153 on the installed host to complete the setup wizard.

verify
labyrinth -version
dig @127.0.0.1 example.com

THE END OF THE THREAD. THE START OF YOUR NETWORK.

Your network.
Your resolver.

One binary. No middleman.
A little more independence.

Make it yours v0.8.44 / PURE GO / MIT

Before you run it / The useful fine print

Transport support

DoT, DoH and DoH3 ship today. DoQ (RFC 9250) is not implemented yet.

Dashboard access

The dashboard binds to 127.0.0.1:9153 by default. Configure web.auth credentials and TLS before exposing it to your network.

Updating & hosting

Read-only installs update at the host level. Labyrinth is a recursive resolver; it does not serve authoritative zones.