How to Create Email With Your Own Domain (Step by Step)

To create email with your own domain, sign up with a business email provider, add your domain, prove you own it with a TXT record, then publish the provider's MX, SPF, DKIM and DMARC records at your DNS host. Once the records check out, create a mailbox for each person, connect webmail, phones and Outlook, and import any old mail. With the domain already registered, it typically takes under an hour.

Before you start: a 5-minute checklist

Gather these first so you don't stall halfway:

• Your domain (for example example.com). If you don't have one, register it at any registrar in the company's name, with auto-renew on.
• Login for your DNS host. This is usually your registrar, but if your nameservers point to Cloudflare or a web host, that is where you edit records. Not sure? Look up your domain's nameservers with any online "NS lookup" tool.
• A list of people and addresses you need: anna@, ben@, plus shared ones like info@, sales@, billing@.
• Your current email situation. Are you moving from Gmail, a cPanel host, Microsoft 365, or starting fresh? This decides the migration step.
• A quiet time window if mail is already flowing on the domain. Switching MX on a Friday evening is less stressful than on Monday morning.

Step 1: Choose an email provider and plan

Pick a service that hosts mail for your domain. Compare it on what you will actually use: storage per mailbox, calendar and contacts, security features (2FA, phishing protection), support for Outlook and phone apps over IMAP/SMTP/CalDAV/CardDAV, migration tools, and how pricing scales per mailbox. Our article on what business email is covers the selection criteria in more detail.

Sign up, choose a plan and enter your domain when asked.

Step 2: Verify that you own the domain

The provider gives you a unique TXT record. Add it at your DNS host. It looks something like:

Type:  TXT
Host:  _verification.example.com   (exact name shown by your provider)
Value: verification=abc123xyz

Then click "Verify" or "Check DNS" in the provider's console. Verification stops anyone else from claiming your domain on the same service. If it fails right away, wait a few minutes — DNS changes take time to propagate — and check again.

Step 3: Publish the mail DNS records

This is the step that makes email actually work. You'll add four core records.

An illustrative set (always copy the exact values from your provider):

example.com.               MX     10 mx.provider.example.
example.com.               TXT    "v=spf1 include:_spf.provider.example ~all"
s1._domainkey.example.com. CNAME  s1.dkim.provider.example.
_dmarc.example.com.        TXT    "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

Tips that save hours of troubleshooting:

• One SPF record only. If an SPF record already exists (for example from your website host or newsletter tool), add the new include: to it rather than creating a second record. Two SPF records make SPF fail.
• Mind the host field. Some DNS panels add your domain automatically, so entering _dmarc.example.com becomes _dmarc.example.com.example.com. If your panel does that, enter just _dmarc.
• Remove old MX records when you are ready to switch. Leaving them means some mail still goes to the old server.
• **Start DMARC at p=none**, read the reports for a few weeks, then tighten to quarantine or reject.

Optional records improve the experience: autoconfig/autodiscover and SRV let Outlook, Thunderbird and phones find server settings automatically; MTA-STS and TLS-RPT require other servers to use encrypted connections when sending to you.

Faster ways to add records

Typing records by hand is where mistakes creep in. Many providers now offer a downloadable zone file you can import into DNS hosts like Cloudflare in one go, or Domain Connect, a standard that applies all records automatically after you log in to your DNS provider and confirm.

Check the records and wait for propagation

DNS changes are often visible within minutes but can take a few hours, depending on TTL values. Use your provider's DNS check page, which should show each record as correct, missing or wrong. If a record stays red, compare it character by character: a missing quote, an extra space or a record on the wrong host name are the usual causes.

Step 4: Create mailboxes, aliases and groups

Now create the addresses:

1. Mailboxes for each person who signs in (anna@example.com). Set a strong temporary password and ask them to change it and turn on two-factor authentication at first login. Send the password through a different channel than email.
2. Aliases for extra addresses that land in an existing mailbox (for example accounts@ delivering to Anna).
3. Groups (distribution lists) when one address should reach several people (team@).
4. A shared mailbox for addresses a team works from together, like support@. Everyone uses their own login, and you can see who replied. See our shared mailbox guide.

If you have many people, use a CSV bulk import if your provider offers one.

Step 5: Connect webmail, phones and desktop apps

Everyone can start in webmail straight away. For other apps:

• Phones: install the provider's app if there is one, or add the account in iPhone Mail or Gmail for Android using IMAP.
• Outlook, Apple Mail, Thunderbird: add an IMAP account. With autodiscover records in place, most apps fill in the server names themselves.
• Calendar and contacts: use CalDAV and CardDAV to sync to phones and Apple Calendar or Thunderbird.

If you use two-factor authentication, desktop apps typically need an app password instead of your normal password.

Step 6: Import your old email and test

If you're moving from Gmail, a hosting account or another provider, import old mail with your provider's migration tool, or drag messages between accounts in a desktop app. Then test properly:

• Send a message from your new address to a Gmail or Outlook.com account and check it lands in the inbox, not spam.
• Open "show original" in Gmail and confirm SPF: PASS, DKIM: PASS, DMARC: PASS.
• Reply from outside to the new address and confirm it arrives.
• Test each alias and group.

How this works on Zomail

In Zomail you add your domain and get a guided DNS page with every record — verification TXT, MX mx.zomail.io, SPF include:_spf.zomail.io, two DKIM CNAMEs (zm1/zm2, with automatic key rotation), DMARC, autodiscover, SRV and MTA-STS — each checked and marked as correct, missing or wrong. You can download the zone file for Cloudflare and similar hosts, or use one-click Domain Connect where your DNS provider supports it. Mailboxes can be added one by one or up to 200 at once from a CSV, and the built-in importer pulls mail from Gmail, Yahoo or any IMAP server. Follow the getting started guide and the email app settings, and see pricing for current per-mailbox rates.

FAQ

Can I create email with my own domain for free?

Some hosting plans include basic mailboxes at no extra cost, and you can technically run your own mail server. Both usually mean weaker deliverability tools, spam protection and support. For a business, a paid provider is usually the more reliable choice. See email for small business for options.

How long until my new email works?

Often within minutes of adding the MX record, but DNS propagation can take a few hours. Allow up to 24–48 hours before assuming something is wrong, and check the records with your provider's DNS checker.

Do I need to transfer my domain to the email provider?

No. Keep the domain wherever it is registered and just edit DNS records there. Transferring is never required to set up email.

Why do my emails go to spam after setup?

Usually SPF, DKIM or DMARC is missing or wrong, or there are two SPF records. Check "show original" in Gmail for pass/fail results, fix any failing record, and give a new domain a little time to build a sending reputation.

Can I keep using Gmail to read my new domain email?

You can add the account to the Gmail app on Android or iPhone, or to any other mail app, over IMAP. Avoid forwarding company mail into a personal Gmail account: it moves business data outside your control and makes offboarding harder.