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.
curl -sSL https://labyrinthdns.com/install.sh | bashLinux & macOS · run as root · includes setup wizard
93.184.216.34Single binary
Cache reads
Cache get
Cached resolve
Cache shards
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.
Single binary
Resolver, dashboard, auth and blocklist engine in one 6.8 MB executable. No runtime dependencies, no cgo, no installer roulette.
Web dashboard
Real-time monitoring, live query stream, cache management and report exports. Dark and light theme, on 127.0.0.1:9153.
DNSSEC validation
Full chain from the root KSK — RSA, ECDSA P-256/P-384, Ed25519 — with aggressive NSEC/NSEC3 synthesis (RFC 8198).
DNS blocklist
Pi-hole style blocking with hosts, domain and AdBlock Plus list formats, auto-refreshed on a schedule you set.
Encrypted transports
DoT on :853, DoH and DoH3 on the web endpoint, EDNS padding on encrypted transports. One flag each in labyrinth.yaml.
Hardened
Bailiwick enforcement (RFC 5452), rate limiting, response rate limiting, and NSEC3 hash budgets that close CVE-2023-50387 / 50868.
Observable
Prometheus metrics, a native Zabbix agent, structured JSON logs and a WebSocket query stream — with RFC-compliance counters.
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.
A window into your resolver
Every answer has a story.
Queries / min
1,240
Cache hit ratio
87%
Blocked today
1,204
Upstream p50
12 ms
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.
waiting for the first query…
Drawn with @xyflow/react · the trace is illustrative, the pipeline is real.
Also in the DNS toolbox
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
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.
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.
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.
| Capability | LabyrinthThis one | Classic resolvers | Public resolvers |
|---|---|---|---|
| Setup | One binary + setup wizard | Packages + hand-edited config | Nothing to run |
| Management | Built-in dashboard | Config files and CLIs | Vendor web console |
| Metrics | Prometheus + Zabbix native | Exporters and plugins | Not yours to read |
| Blocklists | Built-in, Pi-hole style | RPZ zones or extra layers | Up to the vendor |
| Encrypted DNS | DoT · DoH · DoH3 built in | Varies — modules or proxies | Yes — to them |
| Your queries | Stay on your box | Stay on your box | Someone 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 resolution02Can 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 NothingDNS03How 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.
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 benchmarks07 · 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.
curl -sSL https://labyrinthdns.com/install.sh | bash# 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-serviceDownloads 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.
labyrinth -version
dig @127.0.0.1 example.comTHE END OF THE THREAD. THE START OF YOUR NETWORK.
Your network.
Your resolver.
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.