How to connect your domain to business email
Your domain, website host and email provider can be three different services. DNS connects them. To receive mail at [email protected], create the destination mailboxes and publish the records supplied by the email provider at the domain's authoritative DNS service.
Do not begin by replacing every DNS record. A website move and an email move are different changes, and unrelated records may support important services.
Prepare the destination first
Verify the domain with the mail provider if required. Create the users, aliases and shared mailboxes that must receive messages. Confirm storage, account access and how existing mail will be copied.
If you are migrating, keep the old service available during the transition. Decide when users should switch clients and how messages delivered to the old system during DNS caching will be reconciled. Changing MX records does not copy historical messages.
The business email setup guide covers account planning and migration alongside DNS.
Know the records involved
| Record | Email purpose |
|---|---|
| MX | Identifies servers accepting incoming mail for your domain |
| SPF TXT | Authorises sending systems for an envelope-sender domain |
| DKIM TXT or CNAME | Publishes or delegates verification information for signatures |
| DMARC TXT | Expresses policy for authentication aligned with the visible From domain |
| Provider-specific records | May support verification or client discovery |
An MX destination is a hostname, not an IP address. Multiple MX records can be a valid coordinated setup with priorities. Do not mix unrelated providers' destinations unless you have deliberately configured a supported coexistence or migration design.
Publish records in the correct place
Check the domain's authoritative nameservers. The DNS editor at the registrar may not be active if another company hosts the zone. Export the existing records before editing.
Use the exact hostnames, selectors and values provided for your account. Some panels expect @ for the root domain, some an empty field, and others the full name. Check whether the panel automatically appends the domain so you do not accidentally create a duplicated name.
For background, read what DNS is. There is no universal copy-and-paste record that works for every mail service.
Configure sending authentication
Maintain one SPF policy for each relevant sending domain, combining authorised services correctly rather than adding a second SPF record. Include website forms, invoicing, CRM and newsletters in your sender inventory.
DKIM generally requires both publishing the provider's DNS information and enabling signing in the mail service. A record alone does not prove outgoing messages are being signed.
Introduce DMARC with a plan to observe legitimate traffic and progress to enforcement after fixing authentication and alignment. The SPF, DKIM and DMARC guide explains what each mechanism does and why passing one isolated check is not the whole result.
Avoid the proxy mistake
If Cloudflare manages your DNS, normal web proxying does not provide an SMTP mail relay. Hostnames used directly for mail-server connections generally need DNS-only records. MX and TXT records themselves are always DNS-only; there is no orange-cloud switch to turn off on an MX record. Cloudflare's proxy documentation explains the record types.
Follow the email provider's instructions for DKIM and discovery aliases too, especially when a third-party platform must see the original DNS value.
Test real messages in both directions
After the change, check the authoritative records and allow for cached answers. Send to and from external mailboxes, reply to the messages and test role addresses. Inspect authentication results in received headers and try the website's contact form and invoicing system.
A single message landing in the inbox does not guarantee all future delivery. Reputation, content and recipient filtering still matter. Keep bounce messages and timestamps for troubleshooting.
Keep the setup maintainable
Record the purpose of each entry and who owns it. Remove obsolete sending services after the migration, and review authentication when a new tool starts sending mail.
ResaHost's business email service lets you discuss mailbox setup and DNS together. Share the current provider, mailbox count and any external sending tools so the work can be planned around your actual communication needs.