One-click DNS setup for your clients

Adding a domain means adding DNS records, and that is where onboarding can stall. A record pasted into the wrong field, a trailing dot, or a value cut off halfway can all become a support request.

One-click setup removes manual copying for the core mail-hosting records. The domain owner opens the Cloudflare consent screen, reviews the proposed changes, and approves them.

There is one trade-off: the external consent screen identifies TrekMail.

What it does

When a client adds a compatible domain whose DNS is managed in Cloudflare, the dashboard can show an automatic DNS setup button. It sends them to Cloudflare, where the screen lists the records and asks for approval. After they return, TrekMail verifies the DNS before marking the domain ready.

The flow covers the core mail-hosting records used by its current template: MX, SPF, DKIM, and DMARC. It does not replace every optional DNS setting or every branded mail-zone record. Review the consent screen and the DNS status afterward.

The trade-off

The authorization screen belongs to Cloudflare. It names the service asking for the change, and that name is TrekMail.

For that part of setup, your client sees the platform name behind your brand. Before and after it, they return to the dashboard and the normal DNS verification flow.

The trade-off is simple: less copying for a clear, third-party consent screen that names TrekMail.

The consent screen cannot be renamed from the Branding tab. Explain this to clients in advance when the platform name would be unexpected.

When the choice applies

One-click DNS is separate from mail apps on your domain. It configures the standard mail-hosting template for one domain; it does not provision the branded mail-app hostnames.

The button is offered only when the current domain is compatible with the Cloudflare template. It is not offered for a sending-only domain, a domain whose DKIM selector would conflict with the template, a domain already managed through the connected Cloudflare flow, or a DNS provider other than Cloudflare.

For a White Label brand, the feature stays off until you choose otherwise. Turn it on only when the consent-screen disclosure fits your customer onboarding.

Choosing

The switch is in Domains → (your domain) → Branding, at the bottom of DNS for your brand, called One-click setup with Cloudflare. It is off by default for a White Label brand.

Turn it on when the domain uses Cloudflare DNS, the person approving it can review the changes, and it is acceptable for them to see TrekMail on the Cloudflare screen. Save the brand setting first. The option begins working once the White Label trial or subscription is active.

Leave it off when the client needs a fully manual DNS handoff, uses another provider, or should not see the platform name in this part of their setup. They can still use the regular DNS record list and verification controls.

The choice belongs to the brand profile. A shared account-default brand uses the same choice across domains that inherit it; a custom brand can use its own choice.

What your clients see either way

Off: the regular DNS record list, with copy controls and a DNS verification action.

On: the same record list plus the one-click button for compatible Cloudflare domains. The button is optional; a client can still copy records manually.

A client whose DNS is not managed by Cloudflare does not see the button. For them, enabling the brand setting does not change the manual setup path.

What gets added

The Domain Connect template writes the four core mail-hosting records: MX, SPF, DKIM, and DMARC. It does not add every optional DNS record, and it does not configure the branded mail-app zone.

The template is registered to TrekMail and uses the platform record values. That is why White Label makes this an explicit opt-in. If a domain needs a different DNS arrangement, use the manual list and confirm each record in the dashboard instead.

Common questions

"Does this give TrekMail standing access to my client's DNS?" No Cloudflare API token is stored by TrekMail for this flow. The client approves the proposed change in Cloudflare, and TrekMail then checks DNS from the outside to confirm the result.

"Can my client see what will change before approving?" Yes. Review the record list on the Cloudflare consent screen before approving it. If any record is not appropriate for the domain, cancel and use the manual DNS path instead.

"My client uses Cloudflare but doesn't see the button." Confirm that Cloudflare is the DNS provider for the domain, the domain is compatible with the current template, the brand setting is on, and White Label is active. Otherwise use the manual record list.

"Something failed on the Cloudflare screen." A return from Cloudflare is not proof that DNS is ready. Open the domain's DNS status, verify the core records, and use the manual list if anything is missing or wrong.

"Can I turn it on for one client and off for another?" Per brand, not per client. If you run different brands for different clients, each brand carries its own answer. Running multiple White Label brands covers how that works.

"Does turning it off break domains already set up through it?" No. It only decides whether the button is offered next time. Records already published stay exactly as they are.

What's next

• Your name in your customers' mail apps
• Set Up White Label Lite on Your Own Domain
• Stuck on pending DNS?