One-click DNS setup for your clients

Adding a domain means adding DNS records, and that is where onboarding stalls. A record pasted into the wrong field, a trailing dot, a value cut off halfway — each one becomes a message to you.

One-click setup removes the copying. Your client presses a button, approves the change at their DNS provider, and every record lands correctly the first time.

There is one trade-off, and most of this article is about it.

What it does

When a client of yours adds a domain whose DNS is at Cloudflare, they see a button that adds all the records at once instead of a list to copy by hand. Pressing it sends them to Cloudflare, where a screen lists exactly what will be added and asks them to authorize it. They approve, come back, and the domain is configured.

Nothing is typed, so nothing can be mistyped. In our own support numbers this is the single biggest reduction in setup problems — misplaced and truncated records are most of them.

The trade-off

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

So for the few seconds your client is on that screen, they see the platform behind your brand. Everything before and after is yours: your dashboard, your instructions, and the records themselves, which carry your domain rather than ours.

That is the whole trade. Far fewer setup mistakes, against one screen where your name is not the one showing.

We can't brand that screen. Cloudflare identifies the requesting service, and doing it per reseller would mean registering each of you with them separately. If that becomes possible we'll change it.

When the choice applies

It only matters once mail apps on your domain is live.

Until then the records your clients publish name our servers anyway, so a Cloudflare screen saying TrekMail tells them nothing they can't read in the record list. One-click stays available and there is nothing to decide.

Once your DNS branding is live the records carry your name — and then the authorization screen is the only place ours appears. That is the point at which this becomes your call.

Choosing

The switch is in Domains → (your domain) → Branding, called One-click Cloudflare setup. It ships off: we won't put another company's name in front of your clients unless you decide to.

We recommend turning it on. If your clients are not technical, the support time it saves is worth more than a moment on a consent screen. Most people approve it without reading whose name is on it, and the ones who notice are usually the ones who would have managed the manual records anyway.

Leave it off if your clients would recognise the name and ask about it, or if your positioning depends on them never seeing a platform at all. With it off they get the ordinary record list with copy buttons, which works with every DNS provider and reveals nothing.

The setting follows the brand, like the rest of your branding. A brand used across several domains carries one answer for all of them.

What your clients see either way

Off: the records to add, each with a copy button, and a Verify DNS button that checks them once they're in.

On: the same list, plus the one-click button for domains at Cloudflare. The list does not go away — the button is an extra offer, and a client who prefers to add records by hand can ignore it.

Clients whose DNS is anywhere other than Cloudflare never see the button at all. For them, turning this on changes nothing.

What gets added

The same records either way: the MX record that receives their mail, SPF and DKIM so their sending is authenticated, DMARC, and the handful of host records that let mail apps configure themselves.

If your DNS branding is live, these carry your name — your clients publish records pointing at yourbrand.com, not at ours. That is true on the one-click path as much as the manual one; the button adds exactly what the list shows.

Common questions

"Does this give TrekMail standing access to my client's DNS?" No. The change happens once, at the moment they authorize it, and only for the records on that screen. Nothing is left connected and nothing runs afterwards.

"Can my client see what will change before approving?" Yes. Cloudflare lists every record on the authorization screen. Nothing is applied until they press the button.

"My client uses Cloudflare but doesn't see the button." The domain has to sit in the Cloudflare account they're signed into. If they host DNS elsewhere and only proxy through Cloudflare, the button won't appear — the records live somewhere Cloudflare can't change.

"Something failed on the Cloudflare screen." Nothing is applied by halves: either the records went in or they didn't. Have them use the copy-by-hand list and press Verify DNS.

"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?