Navigation

Getting Started

IntroductionQuick Start

Business Setup

What's Business?Launch a BusinessWebApp DeploymentUpdates and ModulesCustom DomainCredits & Top-upsAI Agent

Money

DashNex CreditsDashNex Pay (MoR)Stripe StandardFind Your OrdersTransactionsBalancesPayoutsConversionTransfers

WebApp Modules

OverviewProductsOffersCheckoutsCouponsEmbeddable CheckoutLifecycle EventsDunningPayment MethodsContactsOpt-in FormsEmail BroadcastsEmail LibraryAutomationsTransactionalInboxPages ManagerMenu ControllerMedia LibraryinstraCHATAppearanceAgent SettingsAgent SourcesAgent Q&AConversationsMCPOAuth2 ServerUpcoming Modules

Developers

DashNex CLIDashNex Code
Business Setup

Custom Domain

Connect your own domain to unlock the full capabilities of your WebApp, including custom sender emails and complete DNS management.

Why Add a Custom Domain?

While every WebApp comes with a free DashNex subdomain (e.g., yourbusiness.dashnexcloud.com), adding your own custom domain unlocks additional features:

  • Professional branding with your own domain name
  • Custom sender email addresses (e.g., hello@yourdomain.com)
  • Full DNS management through the DashNex dashboard
  • Automatic SSL/TLS certificate provisioning

Getting Started

To begin, navigate to Settings → Domain in your business dashboard. You have two options:

I have a domain

Connect a domain you already own from any registrar (GoDaddy, Namecheap, Cloudflare, etc.)

I need a new domain

Browse available domains from other DashNex members on the PeerGem Marketplace.

Setup Process

Setting up a custom domain involves three steps:

1

Add Your Domain

Enter your domain name (e.g., example.com). The system will automatically normalize your input—removing any protocol, www prefix, or trailing paths.

When you add the domain, DashNex checks its current nameservers and picks the right setup path for step 2 — either moving nameservers to DashNex, or connecting the Cloudflare account you already use for the domain.

2

Hand Over DNS Control

DashNex needs to manage DNS records for your domain. How this happens depends on where your domain is hosted today — the dashboard detects this automatically when you add the domain and shows you the matching step.

Option A — Configure Nameservers

Domain not on Cloudflare

Update your domain's nameservers at your registrar to the addresses provided by DashNex. This step transfers DNS management to the DashNex platform.

DNS Propagation: Changes typically propagate within minutes to an hour, but can take up to 24 hours in some cases.

Use the Check Status button to verify when your nameservers are active. There's a 60-second cooldown between checks to prevent excessive queries.

Option B — Connect Your Cloudflare Account

Domain already on Cloudflare

If your domain's nameservers already point to Cloudflare, DashNex detects this and switches to the delegated flow instead. You keep your nameservers and your Cloudflare account — nothing moves. You grant DashNex scoped access to that one zone with an API token you create yourself, and DashNex writes the records it needs directly into your existing zone.

Step 2a — Create the API token

Click Open Cloudflare Token Creator. This opens the Cloudflare dashboard with a token template pre-filled for you — named DashNex - yourdomain.com, with all the permissions DashNex needs already selected. Review and create the token in Cloudflare, then copy it.

Under Zone Resources, choose Include → Specific zone → your domain. The token should be scoped to that single zone — it gives DashNex no access to anything else in your Cloudflare account.

Step 2b — Paste the token

Paste the token into the dashboard and click Connect. DashNex verifies it against the Cloudflare API by actually exercising each permission. If anything is missing, the permission list turns red next to the specific permissions that failed, so you can fix the token and try again.

No propagation wait: Because nameservers never change, the domain is ready as soon as the token is accepted. You go straight to step 3.

Once connected, the dashboard shows Cloudflare Connected with a Revoke access link. Revoking deletes the stored token and returns you to this step; you can connect a new token at any time.

3

Choose App Location

Decide where your WebApp will be accessible:

  • Root domain — Your app at yourdomain.com
  • Subdomain — Your app at app.yourdomain.com (or any prefix you choose)

Important: This choice is permanent and cannot be changed later. Choose strategically based on your future plans.

Choosing a subdomain leaves the root domain available for other purposes like a marketing website. Most businesses use the root domain since managing a single app is simpler.

After Setup

Once your custom domain is fully configured, you gain access to additional features:

Sender Emails

Create custom sender addresses for outbound emails from your WebApp:

  • Add sender addresses like hello@yourdomain.com or support@yourdomain.com
  • Set a display name for each sender
  • Enable email forwarding to receive replies at your business email

DNS Manager

Full DNS management directly from your DashNex dashboard:

  • Create, edit, and delete DNS records (A, AAAA, CNAME, MX, TXT, and more)
  • Search and filter records by type, name, or content
  • Changes propagate quickly through Cloudflare's global network

SSL/TLS Certificates

SSL certificates are automatically provisioned and renewed for your custom domain. Your WebApp is always served over HTTPS with no additional configuration required. The edge network handles certificate management entirely.

Removing a Custom Domain

If you need to remove your custom domain, you can do so from the Domain settings page. After removal:

  • Your WebApp reverts to the DashNex subdomain
  • Sender emails associated with the custom domain are removed
  • You'll need to update nameservers at your registrar if you want to use the domain elsewhere

If you connected your own Cloudflare account, there are no nameservers to change — they were never moved. DashNex cleans up the DNS records and the gateway worker it created in your zone, and the stored API token is deleted. The zone itself stays in your Cloudflare account.

Next Steps