A CLI proxy that serves custom DNS records into a Tailscale MagicDNS tailnet
Tailscale's MagicDNS auto-registers hostnames for every device on a tailnet but has no mechanism to inject custom A, AAAA, CNAME, or SRV records. Users who need to resolve internal aliases (e.g. db.internal, api.corp, load-balanced VIPs) across all tailnet nodes today must stand up a full CoreDNS or BIND server and point Tailscale's split-DNS at it -- significant ops overhead for what is fundamentally a small config problem. This CLI sidecar runs as a lightweight local DNS resolver, reads a simple YAML/TOML record file, registers itself as a split-DNS nameserver for a user-chosen suffix via the Tailscale Local API, and answers custom record queries while forwarding everything else upstream. No full DNS server required. One binary, one config file.
Demand Breakdown
Social Proof 1 sources
Gap Assessment
4 tools exist (Headscale custom DNS records, CoreDNS + coredns-tailscale plugin, NextDNS rewrites, tsdproxy) but gaps remain: Requires replacing Tailscale's entire control plane with headscale; incompatible with official Tailscale accounts; no CNAME/SRV support; Requires deploying and operating a full CoreDNS instance; no GUI; no automated split-DNS registration; purely community/unmaintained.
Features8 agent-ready prompts
Competitive LandscapeFREE
| Product | Does | Missing |
|---|---|---|
| Headscale custom DNS records | Supports custom A/AAAA records natively in config.yaml for headscale users | Requires replacing Tailscale's entire control plane with headscale; incompatible with official Tailscale accounts; no CNAME/SRV support |
| CoreDNS + coredns-tailscale plugin | Serves a DNS zone with A/AAAA records for each Tailscale node; allows CNAME via node tags | Requires deploying and operating a full CoreDNS instance; no GUI; no automated split-DNS registration; purely community/unmaintained |
| NextDNS rewrites | NextDNS profile rewrites let users define custom domain aliases; Tailscale can be pointed at NextDNS | Requires a NextDNS subscription; rewrites live in an external SaaS dashboard not co-located with infra; no local-only private records; dependency on third-party resolver |
| tsdproxy | Creates a Tailscale machine per Docker service for proxying traffic | Focused on HTTP reverse proxy per container; does not inject DNS records into the tailnet resolver; no custom record types |
Leads75BUILDER
Sign in to unlock full access.