You can host your website with Omega Digital and use a separate email provider. Use the MX, SPF and DKIM records supplied in that provider’s setup instructions. The examples below show common record formats.
Before you edit anything
Create your mailbox at the external provider first. Verify you can send and receive between users inside their system. Only then swap MX. Otherwise incoming mail bounces during the window where the provider doesn't recognize the domain yet.
Google Workspace
# MX records
Priority Host Value
1 @ ASPMX.L.GOOGLE.COM.
5 @ ALT1.ASPMX.L.GOOGLE.COM.
5 @ ALT2.ASPMX.L.GOOGLE.COM.
10 @ ALT3.ASPMX.L.GOOGLE.COM.
10 @ ALT4.ASPMX.L.GOOGLE.COM.
# SPF (TXT record on root)
@ TXT "v=spf1 include:_spf.google.com ~all"
# DKIM: generate from Admin Console → Apps → Gmail → Authenticate Email
# Add the resulting TXT record at google._domainkey.yourdomain.comMicrosoft 365
# MX record (single)
Priority Host Value
0 @ yourdomain-com.mail.protection.outlook.com.
# SPF
@ TXT "v=spf1 include:spf.protection.outlook.com -all"
# Autodiscover for mail clients
autodiscover CNAME autodiscover.outlook.com.
# DKIM: enable in Microsoft Defender → Policies → Email authentication
# Add CNAMEs for selector1._domainkey and selector2._domainkey as shown thereZoho Mail
# MX records
Priority Host Value
10 @ mx.zoho.com.
20 @ mx2.zoho.com.
50 @ mx3.zoho.com.
# SPF
@ TXT "v=spf1 include:zoho.com ~all"
# DKIM: generate from Zoho Admin → Email Deliverability → DKIM
# Add the TXT at the provided selector, e.g. zoho._domainkey.yourdomain.comFastmail
# MX records
Priority Host Value
10 @ in1-smtp.messagingengine.com.
20 @ in2-smtp.messagingengine.com.
# SPF
@ TXT "v=spf1 include:spf.messagingengine.com ?all"
# DKIM (three CNAMEs)
fm1._domainkey CNAME fm1.yourdomain.com.dkim.fmhosted.com.
fm2._domainkey CNAME fm2.yourdomain.com.dkim.fmhosted.com.
fm3._domainkey CNAME fm3.yourdomain.com.dkim.fmhosted.com.Where to edit records
If your nameservers point to Omega Digital, edit records in cPanel → Zone Editor. Delete the existing MX (pointing to mail.yourdomain.com) before adding the new ones. If your nameservers are at Cloudflare or your registrar, edit there instead.
Turn off local mail delivery on the server
cPanel may continue delivering mail locally after an MX change. Check the domain’s Email Routing setting:
- In cPanel, open Email Routing under the Email section.
- Select your domain.
- Change the routing from Local Mail Exchanger (or Automatically Detect) to Remote Mail Exchanger.
- Save.
Verify the new records
# MX should show the external provider
dig +short MX yourdomain.com
# SPF should include the external provider
dig +short TXT yourdomain.com | grep spf
# DKIM check (replace selector)
dig +short TXT google._domainkey.yourdomain.com
# Send a test email, then check headers:
# dkim=pass, spf=pass, dmarc=passCommon issues
- Old MX records. Remove records for the previous provider when switching email delivery.
- Local mail routing. Set Remote Mail Exchanger when an external provider handles email for the domain.
- SPF hard -all during testing. Use ~all (softfail) while you verify, then switch to -all once delivery is confirmed.
- Multiple SPF records. Only one SPF TXT record is allowed. If you merge providers, combine the includes into one record.
Contact support
Email [email protected] with your domain and the name of your new email provider.