FR: Support custom records in MagicDNS
Also, for DNS, the Customer would really like to make DNS aliases such as **example.ourdomain.beta.tailscale.net** always point to a machine name **staging-1** or something like that. This way, they can easily access the machines.
FL score
out of 100
Verdict
high confidence
Competition
10
competitors found, emerging market, funded players
Trend
No signal yet
A custom DNS record solution for Tailscale's MagicDNS addresses a real pain for developers/sysadmins but faces strong competition and high build complexity.
The pain
The gap
Build angle
Strengths
- Highly specific and articulated pain point for a technical audience.
- Growing market driven by adoption of mesh VPNs and self-hosting.
- Clear value proposition: simplify complex manual DNS management.
Risks
- Direct competitor (NetBird) already offers a similar feature.
- High incumbent strength (Tailscale) could build this feature natively.
- Building a reliable, integrated networking solution is technically complex for a solo builder.
- User willingness to pay for this specific solution might be low due to free alternatives and expected platform features.
- Limited leverage for future projects if tightly coupled to Tailscale.
Next steps
- Conduct in-depth interviews with Tailscale power users to understand their exact pain points, current workarounds, and explicit willingness to pay for a dedicated solution, versus switching to NetBird or waiting for Tailscale's native feature.
- Explore existing Tailscale API capabilities for DNS management. If none exist, prototype a simple external DNS service that can be integrated with Tailscale's split DNS to assess technical feasibility and user experience.
- Analyze NetBird's 'Custom DNS Zones' pricing and feature set closely to identify potential sub-niches or superior UX opportunities.
- Validate if the target audience would prefer a standalone, paid tool over switching to a different mesh VPN that offers the feature natively or continuing with free, manual solutions.
Fly Labs Method
Is the pain real, is there a gap, is it the right time, can one person build it.
- Problem clarity
- 26
- Solution gap
- 13
- Willingness to pay
- 15
- Buildability
- 8
The problem of lacking custom DNS records in Tailscale's MagicDNS is real and specific, causing user frustration. However, the solution space is already being addressed by competitors, and building a deeply integrated solution for Tailscale is complex for a solo builder.
Value Equation
Dream outcome and how likely it feels, against the time and effort it costs.
This idea has an addressable market and clear value proposition but faces strong competition and high build complexity, limiting its profit potential for a solo builder.
One-Person Business
Curiosity pull, identity fit, and a path from free value to paid for a solo creator.
While the problem is clear, the high technical complexity, competitive landscape, and limited creator fit make this a challenging idea for a solo builder.
Viral Frameworks
Hook strength, shareability, and how cheaply it can be tested.
This micro-SaaS has a clear niche but faces high technical risk, strong competition, and moderate challenges in distribution and monetization for a solo builder.
Builder Lens
Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.
This idea addresses a real demand from a specific user group and could simplify a cumbersome status quo, but the narrowest viable solution and future market positioning are challenging due to competition and potential incumbent features.
Why this verdict
Five lenses, one composite. How scoring works
The angle
This weekend
- Conduct in-depth interviews with Tailscale power users to understand their exact pain points, current workarounds, and explicit willingness to pay for a dedicated solution, versus switching to NetBird or waiting for Tailscale's native feature.
- Explore existing Tailscale API capabilities for DNS management. If none exist, prototype a simple external DNS service that can be integrated with Tailscale's split DNS to assess technical feasibility and user experience.
- Analyze NetBird's 'Custom DNS Zones' pricing and feature set closely to identify potential sub-niches or superior UX opportunities.
- Validate if the target audience would prefer a standalone, paid tool over switching to a different mesh VPN that offers the feature natively or continuing with free, manual solutions.
Who is already there, emerging market
NetBird is an open-source alternative to Tailscale that enables users to create secure, private networks based on WireGuard, offering more customization and self-hosting options.
Pricing: Offers a free self-hosted version; cloud-hosted version pricing not explicitly stated but implies paid tiers for advanced features (e.g., identity management integrations beyond default Zitadel).
- HeadscaleVisit
Headscale is an open-source, self-hosted implementation of the Tailscale control server, allowing users to run their own coordination server for Tailscale clients.
Pricing: Free (self-hosted open-source).
- ClouDNSVisit
ClouDNS provides managed DNS services with various features like Anycast DNS, DDoS protection, DNS failover, and support for different record types.
Pricing: Free DNS plan (1 zone, 50 records, 500K queries/month, 1 dynamic DNS hostname). Premium DNS starts from $2.95/month. DDoS Protected DNS starts from $5.95/month. GeoDNS starts from $9.95/month.
- DNSimpleVisit
DNSimple offers domain management and DNS hosting services with features like Anycast DNS, one-click services, alias records, and DNSSEC.
Pricing: Solo plan (for 1 user) is $0.50 per hosted zone per month, plus $0.10 per million queries per zone per month. Offers various tiers with additional features like email forwarding and certificate management.
Amazon Route 53 is a highly available and scalable cloud Domain Name System (DNS) web service that offers domain registration, DNS routing, and health checking.
Pricing: Authoritative DNS: $0.50 per hosted zone per month for the first 25 zones, then $0.10 for additional zones. Standard queries: $0.40 per million queries (first 1 billion per month). Alias queries to AWS services are free.
Google Cloud DNS is a scalable, reliable, and managed authoritative DNS service running on Google Cloud's infrastructure.
Pricing: Managed zone pricing: $0.000273973 per hour per month for 0-25 zones, decreasing with more zones. Queries are charged proportionally to usage, e.g., 1 million queries for $0.40. No free tier.
- No-IPVisit
No-IP provides Dynamic DNS and Managed DNS services, allowing users to maintain consistent access to devices with dynamic IP addresses.
Pricing: Free Dynamic DNS (limited hostnames). Enhanced Dynamic DNS (more hostnames, no expirations) for a few dollars a year. Pro Dynamic DNS starts at $149.99/year for 50 hostnames. Plus Managed DNS starts at $34.99/year for 1 zone. Premium Managed DNS starts at $99.99/year for 1 zone.
Cloudflare Internal DNS (beta) allows organizations to manage DNS records accessible only within their private network, pairing with Gateway resolver policies.
Pricing: Pricing for the beta is not explicitly stated in the provided search results, but Cloudflare generally offers various plans for its broader services.
NordVPN's Meshnet allows users to create secure, private networks to connect devices directly, similar to a mesh VPN, and supports custom DNS configurations.
Pricing: Included with NordVPN subscription (pricing varies based on subscription plan).
UniFi Gateways offer tools to manage DNS resolution within a local network, including creating custom DNS records and assigning local hostnames.
Pricing: Part of the UniFi ecosystem; hardware costs apply for UniFi Gateways. Software features are included with the hardware.
What they charge
Recent news
NetBird v0.63 - Custom DNS Zones for Private Network Resolution
NetBird Blog, January 17 2026
MagicDNS · Tailscale Docs (Update mentions end of support for legacy *.beta.tailscale.net nameserver)
Tailscale Documentation, January 05 2026
I switched from Tailscale to this fully self-hosted alternative, and I'm loving it so far
Ars Technica (via Google Search snippet), June 03 2025
Headscale & Tailscale - Lucas Janin (Blog post discussing DNS configuration in Headscale)
Lucas Janin Blog, January 03 2025
Netmaker: A better alternative to Tailscale VPN
netmaker.io, February 19 2024
Market signals
The market for managing custom DNS records within private, often dynamic, networks is growing, driven by the increasing adoption of mesh VPNs and self-hosted services. Recent updates from competitors like NetBird with "Custom DNS Zones" and ongoing discussions around Headscale's DNS capabilities indicate active development and user demand in this space. While traditional DNS providers offer robust solutions, there's a clear need for integrated DNS management within mesh networking tools to simplify access to internal resources with human-readable aliases. The lack of explicit custom record support in Tailscale's MagicDNS is a notable gap that competitors are addressing.
What frustrates people
- Tailscale's MagicDNS automatically assigns DNS names but does not allow adding arbitrary custom records, forcing users to seek workarounds like external DNS servers or local DNS rewrite rules.
- Setting up and managing DNS aliases for services within a mesh network can be cumbersome, sometimes requiring manual configuration on each client or a separate custom DNS server coupled with a reverse proxy.
- Older Windows environments required registry key modifications (DisableStrictNameChecking) to allow file sharing with DNS aliases, indicating a historical complexity in this area.
- Users of self-hosted solutions like Headscale can encounter DNS conflicts or issues with certificate validation if DNS settings are not correctly configured, especially after server restarts.
- The inability to have different DNS servers per tag or group within some mesh VPN solutions (like Headscale, as noted by one user) limits flexibility for managing different user groups or services.
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: Support custom records in MagicDNS”.