FR: custom domains for magic DNS
### What are you trying to do? As a user, I'd like to point to a custom domain instead of `.beta.tailscale.net`, e.g. `foobar.network`, where `foobar.network` is in my or my org's possession. ### How should we solve this? _No response_ ### What is the impact of not solving this? I use the more cludgy domain than the one and I'm going to have to probably figure out my ssh config strategy all over again ¯\_(ツ)_/¯ ### Anything else? _No response_
FL score
out of 100
Verdict
high confidence
Competition
8
competitors found, mature market, funded players
Trend
No signal yet
A custom domain solution for Tailscale's Magic DNS offers a professional branding upgrade, but requires validation of willingness to pay for a complex integration.
The pain
The gap
Build angle
Strengths
- Clear, specific, and vocal user pain point regarding professionalism and ease of use.
- Identifiable niche audience (Tailscale users) reachable through existing communities.
- Growing market for secure networking solutions and ZTNA.
- Strong value proposition of simplified, professional branding.
Risks
- Significant technical complexity in building a robust, secure, and reliable integration with Tailscale's API and DNS infrastructure.
- Uncertainty around willingness to pay for this specific add-on vs. free workarounds or hoping Tailscale builds it.
- Dependency on Tailscale's API stability and future product roadmap (risk of being natively implemented).
- Potential challenges with certificate management for custom domains within a dynamic network.
Next steps
- Conduct targeted surveys within Tailscale communities (Reddit, forums, Slack) to gauge willingness to pay and feature priorities.
- Create a detailed technical feasibility study for deep Tailscale API integration and DNS management.
- Build a high-fidelity landing page and run ad campaigns to test conversion rates for a hypothetical paid service.
- Interview potential users (SMBs, freelancers using Tailscale) about their current workarounds and budget for this solution.
Fly Labs Method
Is the pain real, is there a gap, is it the right time, can one person build it.
- Problem clarity
- 24
- Solution gap
- 19
- Willingness to pay
- 14
- Buildability
- 10
A real and specific problem exists for Tailscale users wanting custom domains for Magic DNS due to professionalism and complexity issues with default names. There's a clear gap for a simpler solution, but building a robust, integrated product is complex, and willingness to pay might be moderate for this specific feature.
Value Equation
Dream outcome and how likely it feels, against the time and effort it costs.
The idea has good market pain and a clear value proposition for professional users, within a growing market. However, differentiation could be challenging beyond niche focus, and the technical build for deep integration is complex.
One-Person Business
Curiosity pull, identity fit, and a path from free value to paid for a solo creator.
A clear, niche problem with a reachable audience, but the underlying technical complexity and maintenance for a solo builder are significant hurdles.
Viral Frameworks
Hook strength, shareability, and how cheaply it can be tested.
A clear value proposition for a specific, reachable audience, but significant technical and integration risks need careful validation and a robust build.
Builder Lens
Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.
A clear problem with current workarounds for a specific user, demanding a narrow, elegant solution that addresses a growing need for professionalism in secure networking.
Why this verdict
Five lenses, one composite. How scoring works
The angle
This weekend
- Conduct targeted surveys within Tailscale communities (Reddit, forums, Slack) to gauge willingness to pay and feature priorities.
- Create a detailed technical feasibility study for deep Tailscale API integration and DNS management.
- Build a high-fidelity landing page and run ad campaigns to test conversion rates for a hypothetical paid service.
- Interview potential users (SMBs, freelancers using Tailscale) about their current workarounds and budget for this solution.
Who is already there, mature market
- HeadscaleVisit
An open-source, self-hosted implementation of the Tailscale control server that is compatible with official Tailscale clients.
Pricing: Free (open-source, self-hosted)
- NetmakerVisit
An open-source platform that automates virtual networks using WireGuard, offering a self-hosted server/admin UI and private DNS.
Pricing: Open-source (free for community edition); Enterprise and SaaS versions available with additional features (pricing not publicly listed, requires contact).
- FirezoneVisit
An open-source VPN server and egress firewall for Linux built on WireGuard, offering secure remote access and SSO integration.
Pricing: Open-source (free); provides an 'open-core' model, suggesting potential paid enterprise features (pricing not publicly listed).
A Zero Trust security platform that provides secure, identity-first access to private applications and infrastructure, including a tunneling solution.
Pricing: Free (for teams and individuals); Standard ($7/user/month); Enterprise (custom pricing).
An open-source identity-aware proxy that secures access to web applications using identity-driven access controls, offering a clientless solution.
Pricing: Personal (Free); Personal Plus ($5/mo/user); Starter ($6/mo/user); Premium ($18/mo/user); Enterprise (custom pricing); GovCloud (custom pricing).
A Zero Trust Network Access (ZTNA) solution that provides secure remote access by splitting the VPN gateway into Relay and Connector architecture.
Pricing: Starter (Free for up to 5 users); Business (Custom pricing); Enterprise (Custom pricing).
A cloud-based Zero Trust Secure Network as a Service (SaaS) platform that replaces traditional corporate VPNs with a flexible and scalable cloud solution.
Pricing: Essentials ($8/user/month); Premium ($12/user/month); Enterprise (Custom pricing).
- No-IPVisit
Provides Dynamic DNS (DDNS) and Managed DNS services, allowing users to access networks and devices remotely with custom hostnames.
Pricing: Free Dynamic DNS; Enhanced Dynamic DNS ($29.95/year); Pro Dynamic DNS ($44.95/year); Plus Managed DNS ($9.99/month); Premium Managed DNS ($19.99/month).
What they charge
Recent news
Self-Host Headscale on Ubuntu VPS: Build a Private Tailscale VPN Network - MassiveGRID
MassiveGRID, February 05, 2026
Best Tailscale Alternatives (2026) - Techimply
Techimply, March 18, 2026
Top Netmaker Alternatives in 2026 - Slashdot
Slashdot, March 05, 2026
How to Use a Custom VPN with Custom DNS - Windscribe
Windscribe, May 08, 2025
FR: custom domains for magic DNS · Issue #4221
GitHub (Tailscale), March 18, 2022
Market signals
The market for custom domains within secure overlay networks (like Magic DNS) is a growing niche, driven by the increasing adoption of Zero Trust Network Access (ZTNA) and mesh VPN solutions. Recent discussions and feature requests on platforms like GitHub indicate a strong user demand for more flexibility and branding capabilities beyond default domain names provided by services. While the core technology of secure networking is mature, the integration of seamless custom domain support into 'magic' or automated DNS systems within these networks represents an active development area, with both open-source projects and commercial solutions addressing this need.
What frustrates people
- Difficulty in having one domain work both with and without the VPN/mesh network without complex DNS rewrites.
- The inability to easily use custom domains for multiple services on a single node without resorting to ports.
- Concerns about default automatically generated domain names not appearing professional for business use cases.
- The lack of a straightforward way to incorporate custom certificates with custom domains within the VPN network, leading to certificate errors.
- The complexity of integrating custom DNS servers and reverse proxies with mesh VPNs to achieve desired custom domain functionality.
Semble – Code search for agents that uses 98% fewer tokens than grep
Hey HN! We (Stephan and Thomas) recently open-sourced Semble. We kept running into the same problem while using Claude Code on large codebases: when the agent can't find something directly, it falls back to grep, reading full files or launching subagents. This uses a lot of tokens, and often still misses the relevant code. There are existing tools for this, but they were either too slow to index on demand, needed API keys, or had poor retrieval quality.Semble is our solution for this. It combines static Model2Vec embeddings (using our latest static model: potion-code-16M) with BM25, fused via RRF and reranked with code-aware signals. Everything runs on CPU since there's no transformers involved. On our benchmark of ~1250 query/document pairs across 63 repos and 19 languages, it uses 98% fewer tokens than grep+read and reaches 99% of the retrieval quality of a 137M-parameter code-trained transformer, while being ~200x faster.Main features:- Token-efficient: 98% fewer tokens than grep+read- Fast: ~250ms to index a typical repo on our benchmark, ~1.5ms per query on CPU (very large repos may take longer)- Accurate: 0.854 NDCG@10, 99% of the best transformer setup we tested- MCP server: drop-in for Claude Code, Cursor, Codex, OpenCode- Zero config: no API keys, no GPU, no external servicesInstall in Claude Code with: claude mcp add semble -s user -- uvx --from "semble[mcp]" sembleOr check our README for other installation instructions, benchmarks, and methodology:Semble: https://github.com/MinishLab/sembleBenchmarks: https://github.com/MinishLab/semble/tree/main/benchmarksModel: https://huggingface.co/minishlab/potion-code-16MLet us know if you have any feedback or questions!
AI
Postgres extension for BM25 relevance-ranked full-text search
Last summer we faced a conundrum at my company, Tiger Data, a Postgres cloud vendor whose main business is in timeseries data. We were trying to grow our business towards emerging AI-centric workloads and wanted to provide a state-of-the-art hybrid search stack in Postgres. We'd already built pgvectorscale in house with the goal of scaling semantic search beyond pgvector's main memory limitations. We just needed a scalable ranked keyword search solution too.The problem: core Postgres doesn't provide this; the leading Postgres BM25 extension, ParadeDB, is guarded behind AGPL; developing our own extension appeared daunting. We'd need a small team of sharp engineers and 6-12 months, I figured. And we'd probably still fall short of the performance of a mature system like Parade/Tantivy.Or would we? I'd be experimenting long enough with AI-boosted development at that point to realize that with the latest tools (Claude Code + Opus) and an experienced hand (I've been working in database systems internals for 25 years now), the old time estimates pretty much go out the window.I told our CTO I thought I could solo the project in one quarter. This raised some eyebrows.It did take a little more time than that (two quarters), and we got some real help from the community (amazing!) after open-sourcing the pre-release. But I'm thrilled/exhausted today to share that pg_textsearch v1.0 is freely available via open source (Postgres license), on Tiger Data cloud, and hopefully soon, a hyperscalar near you:https://github.com/timescale/pg_textsearchIn the blog post accompanying the release, I overview the architecture and present benchmark results using MS-MARCO. To my surprise, we were not only able to meet Parade/Tantivy's query performance, but exceed it substantially, measuring a 4.7x advantage on query throughput at scale:https://www.tigerdata.com/blog/pg-textsearch-bm25-fu
AI
Consus (YC F24) – LLM gateway for companies handling sensitive data
Hey Hacker News! I'm Eric, the founder of Consus. We route all AI requests to ITAR restricted and controlled unclassified information (CUI) compliant infrastructure. Consus itself satisfies ITAR restrictions, and we recently completed our FedRAMP equivalency audit against the 410 FedRAMP High controls. FedRAMP High is the U.S. government’s strictest security baseline for cloud services handling sensitive unclassified data. A breach of this data could cause severe or catastrophic harm. Achieving FedRAMP equivalency, or authorization, is required before processing CUI information.Demo: https://youtu.be/6MYxJe6P4oYAerospace and defense is experiencing rapid growth. Unfortunately, most companies are struggling to use AI because of necessary data protections & compliance risk. These companies can move even faster if they could use the AI tools that most other industries take for granted.I spent most of my career prior to Consus in aerospace & defense. I launched national security payloads at SpaceX, and was an early employee at Castelion. I’ve watched first hand how compliance red-tape makes it difficult for companies to adopt new technologies and trust vendors that touch their sensitive data. For example, I worked with a satellite manufacturer that doesn’t allow any AI tools, even for non-sensitive work.Even as AI has become extremely useful over the past 9-12 months, I was surprised by how many aerospace & defense companies refused to touch it. They could see how it could be helpful, but they were scared about model providers training on their data, violating an ITAR rule, or risk losing new business because of a failed cyber assessment. These are all rational fears.There were a lot of ways to solve some/all of these problems, but we focused on building a compliant AI inference layer that can "plug" into any AI tool or workflow. Just as OpenRouter integrates with most tools, Consus can connect to tools like ChatGPT or Clau
AI
Questions about this idea?
FlyBot reads the scoring and gives you a second opinion on “FR: custom domains for magic DNS”.