[GH-ISSUE #5790] Netbird as a domain registrar: register and manage custom domains with built-in nameservers #11769

Open
opened 2026-08-05 01:30:55 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @renne on GitHub (Apr 2, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5790

Is your feature request related to a problem? Please describe.

When exposing services through the Netbird reverse-proxy, users who want a branded domain must source it externally. Netbird already provides auto-provisioned subdomains under *.netbird.services, which covers simple cases, but there is no path for users who want their own domain without leaving the Netbird dashboard:

  • Register a domain at a third-party registrar.
  • Point the domain's NS records to Netbird (not currently possible — Netbird offers no public nameservers for custom domains).
  • Create and maintain DNS records manually at an external DNS provider.
  • Repeat for every additional service and domain.

Describe the solution you'd like

Netbird should become a full-featured domain registrar, offering:

  1. Domain registration — users can search for and register custom domains (e.g. mycompany.com) directly from the Netbird dashboard.
  2. Built-in nameservers — registered domains are automatically delegated to Netbird nameservers; no external DNS provider is needed.
  3. Automatic DNS management — when a user creates or removes an HTTP service in the reverse-proxy dashboard, Netbird automatically creates, updates, and deletes the corresponding DNS records.
  4. Automatic TLS — Netbird issues and renews certificates via DNS-01 challenges using its own nameservers, without any user action.
  5. Single pane of glass — domain registration, DNS management, TLS, and service exposure all live in the Netbird dashboard.

Describe alternatives you've considered

  • Auto-provisioned *.netbird.services subdomains: already available and sufficient for simple cases, but do not address the need for branded or business domains.
  • External registrar + DNS provider (e.g. Namecheap + Cloudflare): works today but requires multiple external accounts, manual record management, and no automatic integration with Netbird service lifecycle events.
  • Delegate external domain to Netbird-hosted DNS: a lighter-weight variant (no registration, just nameserver hosting) — acceptable as a stepping stone, but a full registrar experience removes all friction.

Additional context

  • Current reverse-proxy cluster domain: *.netbird.services
  • Auto-provisioned subdomains under *.netbird.services are already supported; this request extends the model to user-owned, Netbird-registered custom domains.
Originally created by @renne on GitHub (Apr 2, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5790 **Is your feature request related to a problem? Please describe.** When exposing services through the Netbird reverse-proxy, users who want a branded domain must source it externally. Netbird already provides auto-provisioned subdomains under `*.netbird.services`, which covers simple cases, but there is no path for users who want their own domain without leaving the Netbird dashboard: - Register a domain at a third-party registrar. - Point the domain's NS records to Netbird (not currently possible — Netbird offers no public nameservers for custom domains). - Create and maintain DNS records manually at an external DNS provider. - Repeat for every additional service and domain. **Describe the solution you'd like** Netbird should become a full-featured domain registrar, offering: 1. **Domain registration** — users can search for and register custom domains (e.g. `mycompany.com`) directly from the Netbird dashboard. 2. **Built-in nameservers** — registered domains are automatically delegated to Netbird nameservers; no external DNS provider is needed. 3. **Automatic DNS management** — when a user creates or removes an HTTP service in the reverse-proxy dashboard, Netbird automatically creates, updates, and deletes the corresponding DNS records. 4. **Automatic TLS** — Netbird issues and renews certificates via DNS-01 challenges using its own nameservers, without any user action. 5. **Single pane of glass** — domain registration, DNS management, TLS, and service exposure all live in the Netbird dashboard. **Describe alternatives you've considered** - **Auto-provisioned `*.netbird.services` subdomains**: already available and sufficient for simple cases, but do not address the need for branded or business domains. - **External registrar + DNS provider (e.g. Namecheap + Cloudflare)**: works today but requires multiple external accounts, manual record management, and no automatic integration with Netbird service lifecycle events. - **Delegate external domain to Netbird-hosted DNS**: a lighter-weight variant (no registration, just nameserver hosting) — acceptable as a stepping stone, but a full registrar experience removes all friction. **Additional context** - Current reverse-proxy cluster domain: `*.netbird.services` - Auto-provisioned subdomains under `*.netbird.services` are already supported; this request extends the model to user-owned, Netbird-registered custom domains.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11769