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.
Email and the website are independent. A domain can keep mail on Google or Zoho and the website on Squarespace or Shopify. Changing one does not move the other.
Open the wizard
- Log in to the Texo client area
- Go to Domains (My Domains)
- Click DNS Wizard next to the domain
You can also open Tools, then DNS Wizard, then pick the domain at the top.
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 — after a transfer, or when you switch nameservers. Live email and the live website stay as they are until then. 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, Fastmail, Mimecast, iCloud, Titan, Cloudflare Email, or other)
- SPF & DMARC — whether those two mail-trust records exist and look healthy
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.
Under the health cards, pick a task:
Verify a domain or authorise a sender
Use this when Google, Microsoft, Amazon SES, 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, Shopify, or Other know you own the domain
- Authorise a sending service — Mailchimp, SendGrid, Amazon SES, Resend, 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.
google-site-verification= value, then Create DNS.The same idea applies to Microsoft 365 (MS=ms…), Facebook, Apple, Zoho, Pinterest, Atlassian, Yandex, Proton and LinkedIn. Shopify usually uses host shopify_verification. Use Other when the provider is not listed — paste Type, Host, and Value exactly as they showed.
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.
em… CNAME, not as a second apex SPF. Use + Add another record if they listed more. Do not invent host names.What Create DNS will and will not do
- CNAME and ordinary TXT are published exactly as pasted
- An apex SPF (
v=spf1orinclude:) is merged into the one existing SPF. You never get a second SPF, and+allis never added - A second
_dmarcis skipped if one already exists - Apex MX is never changed from this task — mailboxes stay put. A sending service may add bounce MX on a subdomain such as
send(Resend). That does not move mailboxes - 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, Proton Mail, Fastmail, Mimecast, iCloud Mail, Titan, or Cloudflare Email. This does change MX and SPF, and it adds a basic DMARC if none exists. Changing email does not move the website.
Amazon SES, Mailchimp, SendGrid and Resend are not on this list — they send mail as you; they do not host the mailbox. Use Authorise a sending service for those.
Pick a host. A short preview lists the records that will change. Click the same chip again if you want to cancel. If nameservers are not Texo yet, the preview is Keep email on… or Prepare email on… — records are written in Texo's zone and go live when nameservers switch.
If that host is already current, the button re-applies the same records — useful after a messy zone. Changing MX asks you to confirm.
When you point email to Texo, mail is this account's cPanel IP (the same IP already on cpanel / webmail), never the website's A record. Optional extras: DKIM rows copied from the provider's admin, and Microsoft 365 Autodiscover / Skype-for-Business CNAMEs if you need them.
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,
wwwCNAME 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
- Webflow, Framer, Carrd — known defaults. Confirm against the values that builder showed you
- Other — paste A / CNAME from any other host
When the domain already uses Texo nameservers, the current web host is shown as a badge and cannot be selected again. When nameservers are still elsewhere (a transfer in), the live website chip is selectable — that copies the live apex A and www into the Texo zone so the site keeps working after the switch.
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.zaandns2.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.
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.
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, Amazon SES, or Resend without moving email? Yes. Use Authorise a sending service, not Point email. Point email is only for moving mailboxes. Amazon SES wants three DKIM CNAMEs; Resend uses a bounce host on send, not the domain apex.
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.
The domain is transferring in and nameservers are not Texo yet. You can still write email and website records in Texo's zone now. They go live when nameservers switch. Live mail and the live website stay as they are until then.
Stuck? Submit a support ticket.