I built a DNS resolver from scratch in Rust – no DNS libraries

I built a DNS resolver that lets me use https://frontend.numa instead of localhost:5173 — auto-generated TLS certs, WebSocket passthrough, path routing. No mkcert, no nginx, no /etc/hosts.

Hacker NewsApr 2ToolDesign & CreativeSource

FL score

out of 100

Verdict

BUILD

high confidence

Competition

competitors found, mature market, funded players

Trend

No signal yet

A Rust DNS resolver simplifying local web development by eliminating mkcert/nginx/hosts, but faces a crowded market and high build complexity.

The pain

Developers struggle with complex local development setups involving TLS certificates, custom domains, and proxy configurations using tools like mkcert, Nginx, or /etc/hosts. These lead to debugging difficulties, steep learning curves, and general frustration, especially in modern microservice architectures.

The gap

While many tools exist (ngrok, Traefik, Caddy), they often introduce their own complexities (learning curves, external dependencies, cost, reliability issues). The gap is for an extremely simple, single-tool solution that handles auto-TLS, custom domains, and routing without requiring a patchwork of traditional networking tools.

Build angle

A self-contained, high-performance DNS resolver in Rust that intercepts and routes local traffic, automatically generating TLS certificates and providing simple path-based routing, aiming for a zero-config-like developer experience.

Strengths

Addresses a specific, frequently encountered pain point for developers (local dev setup complexity).
High technical skill demonstrated by building a DNS resolver from scratch in Rust.
Clear payment signals in the market for developer tools that save time and reduce friction.
The underlying problem (local dev complexity) is growing, making the solution more relevant over time.

Risks

Very high build complexity for a solo founder to achieve a production-ready, reliable system.
Extremely crowded market with many well-funded, established competitors (ngrok, Traefik, Caddy, Cloudflare Tunnel).
The 'from scratch in Rust' technical angle might not translate into a clear, compelling *user benefit* that justifies switching from existing, robust solutions.
Difficulty standing out and acquiring users in a mature market unless the simplicity and reliability are truly revolutionary.
Maintaining a low-level DNS resolver and proxy with modern web features could be a long-term burden for a solo developer.

Next steps

Conduct in-depth user interviews with target developers to confirm how painful existing solutions are, specifically around mkcert, Nginx, and /etc/hosts, and if they'd pay to replace them.
Build a very narrow MVP that solves *only one* critical aspect (e.g., auto-TLS for a single local service on a custom domain) and get it into a few users' hands for feedback.
Validate the specific claim of 'no mkcert, no nginx, no /etc/hosts' is a strong enough differentiator to overcome switching costs from deeply embedded existing workflows.
Explore integrating with existing developer ecosystems (e.g., Docker, VS Code extensions) to simplify adoption rather than asking developers to replace core infrastructure.

Fly Labs Method

Is the pain real, is there a gap, is it the right time, can one person build it.

Problem clarity: 25
Solution gap: 13
Willingness to pay: 20
Buildability: 10

A DNS resolver in Rust simplifying local dev setup has strong problem clarity and payment signals but faces a crowded market and high build complexity for a solo founder.

Value Equation

Dream outcome and how likely it feels, against the time and effort it costs.

Good market pain and value proposition, but high build complexity and a crowded market present significant hurdles for differentiation and GTM.

One-Person Business

Curiosity pull, identity fit, and a path from free value to paid for a solo creator.

Clear problem and good leverage, but audience reach, creator fit, and product simplicity for a solo builder in a competitive market are concerns.

Viral Frameworks

Hook strength, shareability, and how cheaply it can be tested.

Clear value prop for a specific dev audience, but high assumption risk regarding switching behavior and competitive landscape.

Builder Lens

Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.

Strong demand and specificity for a pain point that will grow, but the narrowest wedge and proof of unique solution effectiveness are key to validate.

Why this verdict

The idea targets a real and specific pain point for developers, and the market shows a willingness to pay for solutions that simplify their workflow. However, the competitive landscape is extremely crowded with funded players and established open-source tools. Building a DNS resolver from scratch is a significant technical undertaking for a solo founder, posing risks to speed-to-market and long-term maintenance. The key risk is whether the 'no mkcert, no nginx, no /etc/hosts' promise is a strong enough differentiator to motivate developers to switch from proven, albeit complex, alternatives. Extensive validation is needed to determine if this specific angle genuinely captures an unserved, paying niche or if it's merely a technically impressive but strategically challenging endeavor.

Five lenses, one composite. How scoring works

The angle

This weekend

Conduct in-depth user interviews with target developers to confirm how painful existing solutions are, specifically around mkcert, Nginx, and /etc/hosts, and if they'd pay to replace them.
Build a very narrow MVP that solves *only one* critical aspect (e.g., auto-TLS for a single local service on a custom domain) and get it into a few users' hands for feedback.
Validate the specific claim of 'no mkcert, no nginx, no /etc/hosts' is a strong enough differentiator to overcome switching costs from deeply embedded existing workflows.
Explore integrating with existing developer ecosystems (e.g., Docker, VS Code extensions) to simplify adoption rather than asking developers to replace core infrastructure.

Who is already there, mature market

ngrokFundedVisit
A cloud-based service that provides secure tunnels to expose local servers to the internet.
Pricing: Free tier with up to 3 online endpoints, 1GB data, 20k HTTP/S requests. Personal plan: $8/month (billed monthly) or $5/month (billed annually) for 3 active endpoints, 10 GB/month bandwidth, 60,000 requests/month. Pro plan: $49/month (billed monthly) or $29/month (billed annually) for 10 active endpoints, 50 GB/month bandwidth, 500,000 requests/month. Enterprise pricing starts from $5,000–$15,000 annually.
TraefikFundedVisit
An open-source Edge Router that makes publishing services a fun and easy experience.
Pricing: Open-source version is free. Traefik Enterprise starts at $2,000 annually per instance, offering advanced features, technical support, and increased security.
CaddyFundedVisit
A powerful, enterprise-ready, open-source web server with automatic HTTPS.
Pricing: Open-source and free to use. Enterprise solutions available, but specific pricing not listed in search results.
Nginx Proxy ManagerVisit
A web-based interface for managing Nginx proxy hosts with free SSL.
Pricing: Free and open-source.
zrokFundedVisit
An open-source sharing solution providing private and public secure tunneling using OpenZiti for zero-trust networking.
Pricing: Free tier (ZrokNET STARTER) includes 5 Daily GB, 2 Environments, up to 5 Share Backends (2 Reserved), 5 Private Access Frontends. Paid plans start at $20/month for 100 Daily GB, 50 Environments, 100 Share Backends, 100 Private Access Frontends, and custom domains.
LocalXposeVisit
A reverse proxy tool that provides a public URL to localhost with support for HTTP/S, TCP/TLS, and UDP tunnels.
Pricing: Offers a free tier with 2 active HTTP tunnels and persistent subdomains. Specific pricing for paid tiers not found in search results.
LocaltunnelVisit
An npm package that lets you create HTTP/HTTPS tunnels to localhost, providing a random subdomain.
Pricing: Free.
Cloudflare TunnelFundedVisit
Creates secure, outbound-only connections between your services and Cloudflare's edge network.
Pricing: Included with Cloudflare plans, which have a free tier. Specific pricing for advanced tunnel features not explicitly detailed as standalone in search results.
TailscaleFundedVisit
A mesh VPN solution that connects devices directly using WireGuard and offers secure public URL exposure via Tailscale Funnel (beta).
Pricing: Free tier for individuals. Paid plans start at $6/user/month for teams. Specific pricing for 'Funnel' feature not explicitly detailed as standalone.
sishVisit
An open-source ngrok/serveo alternative that provides HTTP(S)/WS(S)/TCP tunnels to localhost using only SSH.
Pricing: Free and open-source.
TelepresenceFundedVisit
A tool that creates a network bridge between a developer's local machine and a remote Kubernetes cluster for local development and debugging.
Pricing: Free tier and paid enterprise plans. Specific pricing for paid tiers not found in search results.
mirrordFundedVisit
A tool that allows developers to run local processes within their cloud environment by intercepting calls at the process level.
Pricing: Free.

Funded players

What they charge

The pricing landscape is diverse, ranging from completely free and open-source solutions (e.g., Localtunnel, Caddy, Nginx Proxy Manager) to freemium models with usage-based billing (e.g., ngrok, zrok) and enterprise-grade paid subscriptions (e.g., Traefik Enterprise). Free tiers typically offer basic tunneling with limitations on bandwidth, endpoints, and features like custom domains. Paid plans introduce increased limits, advanced security features (e.g., SSO, IP restrictions), dedicated support, and custom branding. Some solutions, like LocalCan, have explored one-time payment models, though this appears less common for services with ongoing infrastructure costs.

I built a DNS resolver from scratch in Rust – no DNS libraries

Every CEO and CFO change at US public companies, live from SEC

Simplified AI image creation tool for non-designers

µJS, a 5KB alternative to Htmx and Turbo with zero dependencies