Texo DNS Wizard User Guide

The DNS Wizard is the place in the Texo client area to check a domain's public DNS, add the records a provider asked for, move mail, point the website, or switch nameservers. It writes the Texo zone only — it does not change Cloudflare or another host's DNS.

Open the wizard

Log in to the Texo client area
Go to Domains → My Domains
Click DNS Wizard next to the domain

My Domains list with a DNS Wizard button next to each domain — My Domains — click **DNS Wizard** next to the domain.

You can also open Domains → DNS Wizard from the menu, then pick the domain at the top.

Domain picker at the top of the DNS Wizard — If you opened the wizard from the menu, choose the domain here.

You can prepare records here as soon as the domain has a zone on Texo (a DNS file on our servers). Those records only go live on the internet after the domain uses ns1.texo.co.za and ns2.texo.co.za. If nameservers still point somewhere else, finish the zone first, then switch nameservers when you are ready.

What you see first

The top of the page is a health check of public DNS — what the internet sees right now:

Nameservers — who answers for the domain, and whether that is Texo
MX — where mailboxes live (Texo, Microsoft 365, Google, Zoho, Proton, or other)
SPF & DMARC — whether those two mail-trust records exist and look healthy

Nameservers card showing Texo ns1 and ns2 — Nameservers — this domain uses Texo.

MX card showing mail hosted by Texo — MX — email is on Texo.

If SPF or DMARC is missing and the zone is on Texo, use Click to Fix. That writes a safe baseline (a simple allow-list for Texo mail, and a DMARC policy of none). It does not invent provider tokens and it does not move your mail.

SPF and DMARC missing with Click to Fix buttons — SPF or DMARC missing — **Click to Fix** writes the baseline on the Texo zone.

Under the health cards, pick a task:

The four DNS Wizard tasks: verify, point email, connect a website, update nameservers — Open the task you need. Click the same heading again to close it.

Verify a domain or authorise a sender

Use this when Google, Microsoft, Mailchimp, or another service asks you to add a DNS record to prove you own the domain or to let them send mail as you. Mailboxes stay where they are. To move mail, use Point email instead.

Open I need to verify my domain at…

Verify domain ownership — one code so Google, Microsoft 365, Meta, Apple, Zoho, Stripe, Pinterest, Atlassian, Yandex, Proton, LinkedIn or Shopify know you own the domain
Authorise a sending service — Mailchimp, SendGrid, Brevo, HubSpot, or Other. These add DKIM (and sometimes SPF / DMARC). They do not move your mailbox

Ownership

Paste exactly what the provider showed you. Most want an apex TXT (host @). Stripe and Shopify also ask for a host name, not only the value.

The same idea applies to Microsoft 365 (MS=ms…), Facebook, Apple, Zoho, Pinterest, Atlassian, Yandex, Proton and LinkedIn. Shopify usually uses host shopify_verification.

Sending services

Each chip opens only the empty rows that provider normally lists. Leave unused rows blank. Use + Add another record if they showed more. Copy DKIM host names from the provider — do not invent them.

Chip	Rows you get
Mailchimp	2 × CNAME (DKIM) + TXT `_dmarc`
SendGrid	3 × CNAME (default Automated Security)
Brevo	TXT `@` (brevo-code) + 2 × CNAME + TXT `_dmarc`
HubSpot	2 × CNAME + TXT `@` (SPF) + TXT `_dmarc`
Other	1 × CNAME + 1 × TXT, then add more

SendGrid three CNAME sender records in the DNS Wizard — SendGrid — usually three CNAMEs. Their SPF sits on the `em…` CNAME, not as a second apex SPF.

What Create DNS will and will not do

CNAME and ordinary TXT are published exactly as pasted
An apex SPF (v=spf1 or include:) is merged into the one existing SPF. You never get a second SPF, and +all is never added
A second _dmarc is skipped if one already exists
MX is never changed from this task — mailboxes stay put
CNAME is not allowed on @ (that would break the zone)

If you type host @, it is stored as the real domain name in cPanel.

Existing records

Ownership and sender records already on the Texo zone appear under Existing records.

Click the value to edit it, then Save
Click ×, then Remove, to delete

Mailbox DKIM (v=DKIM1), SPF and DMARC are not edited from this list. Use Point email or Click to Fix for those.

Point email

Open I want to point my email to… when mailboxes should live at Texo, Microsoft 365, Google Workspace, Zoho Mail, or Proton Mail. This does change MX and SPF, and it adds a basic DMARC if none exists.

Pick a host. A short preview lists the records that will change. Click the same chip again if you want to cancel.

If that host is already current, the button re-applies the same records — useful after a messy zone.

Optional extras: DKIM rows copied from the provider's admin, and Microsoft 365 Autodiscover / Skype-for-Business CNAMEs if you need them.

Point email to Google Workspace with preview of records — Point email — pick a host, read the preview, then apply. Mailboxes follow MX.

Connect a website

Open Connect this domain to… to point website DNS only. Mail stays where it is.

Texo — A record to this account's hosting IP, www CNAME to the domain
Shopify — Shopify's A / CNAME pair
Squarespace — Squarespace verify + site targets
Wix — pointing (recommended) keeps Texo mail. Switching to Wix nameservers moves all DNS to Wix, so mail has to be rebuilt there
Other — paste A / CNAME from Webflow, Framer, Carrd, and so on

The current web host is shown as a badge and cannot be selected again.

Connect website to Shopify in the DNS Wizard — Website — Shopify selected. Email is left on Texo in this example.

Update nameservers

Nameservers tell the internet which company answers DNS for the domain. If the domain is registered with Texo, this task can change them at the registrar.

Texo — one click to ns1.texo.co.za and ns2.texo.co.za
Custom — paste another host's nameservers

If the registrar will not accept an automated change, the wizard opens a support ticket instead.

A registered .za domain cannot have empty nameservers at ZACR. That is normal — you replace them, you do not blank them.

Update nameservers task in the DNS Wizard — Nameservers — switch to Texo or enter custom NS.

Dead domains

A dead domain has no public nameservers, so the internet cannot find who answers for it. That is not the same as "parked" or "expired" — the domain simply does not resolve.

The wizard then walks two steps:

Create a Texo zone — park on an existing cPanel account, create a cPanel account (resellers), or order hosting
Set Texo nameservers — so the new zone is what the world uses

Until step 2 finishes, DNS records you create on Texo are ready but not live.

Dead domain banner and Step 1 park or order choices — Dead domain — no public NS. Create a zone first, then point nameservers at Texo.

FAQ

I created DNS records but they do not work yet. The domain must be using Texo's nameservers for the DNS records to be live. After that, the internet can take a few minutes to a few hours to catch up.

Can I add Mailchimp without moving email? Yes. Use Authorise a sending service, not Point email. Point email is only for moving mailboxes.

I pasted the wrong token. Under Existing records, click the value, edit it and Save, or click × then Remove.

Will this change Cloudflare? No. The wizard writes the Texo cPanel zone only. If the domain uses Cloudflare nameservers, add the same records in Cloudflare instead.

Wix nameservers? Mail will break unless you copy MX, SPF, DKIM and DMARC into Wix. Pointing (A/CNAME) is safer if you want Texo mail.

Stuck? Submit a support ticket.

Texo DNS Wizard — User Guide