Connect a Domain to a Website Without Breaking Email

Last updated
Save as PDF

Connect a domain by changing only the A and CNAME records your website provider gives you. Save the current DNS first, and leave MX and email-related TXT records unchanged. Your website and email can use the same domain because they rely on different records. Avoid changing nameservers unless you intend to move all DNS management.

Before You Connect the Domain

Collect this information before editing DNS:

Domain registrar: the company where the domain was purchased.
Active DNS host: the company named in the domain’s current nameservers.
Website provider: Shopify, Squarespace, ZenBusiness Website Builder, or another platform.
Email provider: ZenBusiness Business Email, Google Workspace, Microsoft 365, or another service.
Website records: the exact A and CNAME values shown in the website provider’s current connection screen.

Take screenshots of the nameservers and every A, CNAME, MX, and TXT record. If the website connection fails, these screenshots provide a rollback reference and help support see what changed.

Edit records at the active DNS host. If the nameservers point to ZenBusiness, use zenbusiness.com → Web Tools → Domains → DNS Management. If they point to Cloudflare, GoDaddy, Squarespace, or another provider, make the changes there instead.

Know Which Records to Change

Record	Usually controls	What to do during a website connection
A	Root domain, such as `example.com`	Replace only the root-domain value required by the website provider
CNAME	A subdomain, often `www`	Replace or add only the provider-required hostname
MX	Incoming email	Preserve it unless the email provider gives replacement instructions
TXT	Verification, SPF, and DKIM	Preserve existing email records; add only exact new verification values
Nameservers	Where all DNS is managed	Change only when intentionally moving every DNS record to another host

Never clear the entire DNS list before connecting a website. Deleting MX or TXT records can stop email or cause messages to fail authentication. If your website provider asks you to change nameservers, recreate all required website and email records at the new DNS host before the switch.

Connect a ZenBusiness Domain to Shopify or Another Website

Use the values shown in the website provider’s current domain-connection screen. Provider IP addresses and hostnames can change, so do not rely on values copied from an older article.

Open the website provider’s domain settings and choose the option to connect an existing domain.
Copy the required A record for the root domain and CNAME record for www.
At zenbusiness.com, go to Web Tools → Domains, select the domain, and open DNS Management.
Update the matching A and CNAME records. Do not delete MX or existing email-authentication TXT records.
Save, then return to the website provider and start its verification step.
Wait for propagation and test both example.com and www.example.com.

If ZenBusiness Business Email was working before the website change, send and receive a test message after the website connects. A working website does not prove that email records were preserved.

Connect a GoDaddy, Namecheap, or Squarespace Domain to ZenBusiness Website Builder

A domain registered elsewhere stays with that registrar. The DNS changes happen at the active DNS host, while ZenBusiness Website Builder supplies the values.

At zenbusiness.com, open Web Tools → Website Builder → Connect Domain and choose a domain from another provider.
Copy the A and CNAME values shown for your site.
Sign in to the active DNS host:
GoDaddy: My Products → Domains → Manage DNS
Namecheap: Domain List → Manage → Advanced DNS
Squarespace: Settings → Domains → select the domain → DNS Settings
Update the root A record and www CNAME using the exact ZenBusiness values.
Preserve the domain’s existing MX and email-authentication TXT records.
Save, wait for propagation, and finish verification in Website Builder.

ZenBusiness Business Email cannot be created on a domain registered outside ZenBusiness. Keep using the domain’s current email provider or choose a third-party provider that supports externally registered domains.

If the Provider Requires Nameserver Changes

A nameserver change moves control of all DNS records, not just the website. Before switching, copy every active A, CNAME, MX, and TXT record into the new DNS host. Confirm that both the website and email provider’s required records are present there.

After nameservers change, stop editing DNS at the old provider. Its records may remain visible but no longer control the domain. Nameserver changes can take 3–5 days to propagate. During that period, some visitors or email senders may reach the old configuration while others reach the new one.

Most website connections do not require a nameserver move. If the provider also offers an A/CNAME connection, use that narrower method to reduce risk.

Verify the Website and Email

DNS record changes can begin appearing within a few hours and may take 24–48 hours to propagate broadly. Use a public lookup such as WhatsMyDNS to confirm that the expected A, CNAME, and MX records are visible.

Test all connected services:

Open the root domain without www.
Open the www version.
Send a message to the business email address.
Reply from the business inbox.
Complete any verification step shown by the website provider.

If the website works but email fails, compare MX and TXT records with the email provider’s current instructions. If email works but the website fails, compare the root A and www CNAME with the values shown in the website platform.

Troubleshoot a Failed Connection

If the website shows “connection refused,” remains pending, or opens the old site, verify that the site is published and that you edited DNS at the active nameserver provider. Check the root and www records separately; one can be correct while the other is not.

Do not repeatedly replace records during the propagation window. Save the exact error, the time of the last change, and screenshots of the website connection screen and DNS records. If records match after 48 hours but the site still fails, contact our support team with that information. Support may need to review the Website Builder connection or domain configuration.

Frequently Asked Questions

Will connecting my domain to a website break my email?

It should not if you change only the website’s A and CNAME records. Incoming email uses MX records, while SPF and DKIM commonly use TXT records. Save the current DNS first, preserve MX/TXT records, and use only the exact A/CNAME values shown by the website provider.

Which DNS records should I change for Shopify?

Use the current A and CNAME values shown in Shopify Admin under the domain connection settings. Update those matching records at the active DNS host and preserve MX/TXT records. Do not copy a Shopify IP address or hostname from an older article because provider requirements can change.

My domain is at GoDaddy. Can I use ZenBusiness Website Builder?

Yes. Open Web Tools → Website Builder → Connect Domain and copy the A and CNAME values for your site. Then sign in to GoDaddy → My Products → Domains → Manage DNS and add those exact values. Leave the domain at GoDaddy and preserve its email records.

My domain is at Namecheap or Squarespace. Can I connect it to ZenBusiness?

Yes. Get the current A and CNAME values from Web Tools → Website Builder → Connect Domain, then enter them at the domain’s active DNS host. The domain remains registered with Namecheap or Squarespace. Preserve existing MX/TXT records and finish the connection check in Website Builder.

Why does my website work but my email stopped?

The website’s A/CNAME records may be correct while email MX or TXT records are missing at the active DNS host. Compare the current records with your email provider’s instructions. If you use ZenBusiness Business Email, contact support to verify or restore its supported DNS configuration rather than guessing MX values.

Why does `www` work but the root domain does not?

The www CNAME may be correct while the root A record is missing or points elsewhere. Compare both values with the website provider’s connection screen. The reverse can also happen: the root works while www fails. Test both addresses after propagation before treating the connection as complete.

Do I need to change nameservers to connect a website?

Usually no. Most platforms can connect through individual A and CNAME records. Change nameservers only when the provider specifically requires a full DNS move. Before switching, recreate all website and email records at the new host because the old DNS screen will no longer control the domain.

How long does a domain connection take?

A/CNAME changes can begin appearing within a few hours and may take 24–48 hours to propagate broadly. Nameserver changes can take 3–5 days. Avoid making repeated edits while changes are propagating. Check public DNS and test both the root and www addresses before changing records again.

What should I send support if the connection still fails?

Send the domain, registrar, active DNS host, website provider, email provider, current nameservers, screenshots of A/CNAME/MX/TXT records, the website connection screen, the exact error, and when records changed. Also say whether the website and email worked before. This lets support separate DNS, publishing, and email issues.

Still Need Help?

If the required records are publicly visible but the website still does not connect after the propagation window, contact our support team with the troubleshooting details above.