Production DNS.
On your laptop.

You're building something that depends on domain routing. Multi-tenant SaaS where acme.myapp.com goes to one tenant and beta-corp.myapp.com goes to another. Or a platform with custom domains — your customer maps store.acme.com to your app. In production, this works because DNS resolves the domain to your server. In development, it doesn't — because myapp.test resolves to nothing.

Donk runs a lightweight DNS server on your machine. Each server you register gets its own loopback IP — 127.0.0.2, 127.0.0.3, etc. — so you can run multiple servers on the same port without conflicts. Create A-records that point any custom domain to any server's IP. Enable wildcard resolution for *.myapp.test. Every device on your LAN resolves through Donk's DNS.

• Per-server loopback IPs — multiple servers on port 443, no conflicts
• Custom A-records — map any domain to any server
• Wildcard DNS resolution for subdomain-based routing
• Live query log — every DNS lookup color-coded: LOCAL, FORWARDED, BLOCKED
• Multi-device — phones, tablets, colleague laptops resolve your custom domains
• Network-wide ad and tracker blocking — blocklist toggle
• Non-local queries forwarded transparently — the internet still works