How to Set Up Business Email on Your Domain, Step by Step

Setting up business email is not hard, but the order of the steps matters. If you change DNS records before the mailboxes exist, incoming messages can bounce. If you skip the authentication records, your first outgoing messages may land in spam. This guide walks through the process in a safe order for a domain you already own.

Before you start

Collect the following so you do not have to hunt for them halfway through:

• Login details for wherever your domain's DNS is managed (the registrar, your host, or a service such as Cloudflare).
• A list of the addresses you need and who will use each one.
• Details of any existing email on the domain. If there is already mail in use, do not change MX records until your new mailboxes are ready and any old messages are copied.

The setup steps

Step 1: create the mailboxes

In your hosting control panel, create a mailbox for each person. In Plesk this is done from the Mail section of the subscription. For each mailbox choose a strong, unique password and set a storage limit that suits the person's use. Create role addresses such as info@ either as mailboxes or as aliases that deliver to an existing mailbox. If you are unsure which to use, read our article on forwarding versus aliases versus mailboxes.

Step 2: find out which DNS records you need

Your provider should give you the mail server hostname for your MX record and the text of the SPF record. DKIM keys are generated on the mail server, and the panel shows you the TXT record to publish. If your DNS zone is managed on the same server as your hosting, many of these records are created for you. If the zone is managed elsewhere, you add them by hand.

Step 3: add the DNS records

Record	Purpose	Where
MX	Tells senders which server receives your mail	Domain root
A or CNAME for the mail host	Gives the MX target an IP address	For example, the mail subdomain
TXT (SPF)	Lists servers allowed to send for your domain	Domain root
TXT (DKIM)	Publishes the public key for signatures	selector._domainkey
TXT (DMARC)	Sets the policy for failed checks	_dmarc

Remove old MX records that point to a previous provider, unless you intentionally want a backup route. Mixed MX records sending mail to two different systems are a common reason messages seem to vanish. To lower the risk, reduce the TTL on the old records a day beforehand, as explained in our TTL article.

Step 4: connect your devices

Use these settings on your phone or desktop client, replacing the hostname with the one your provider gives you:

• Username: the full email address
• Incoming: IMAP, port 993 with SSL/TLS
• Outgoing: SMTP, port 587 with STARTTLS (or 465 with SSL/TLS)
• Authentication: required for outgoing mail

Using IMAP keeps messages on the server so every device sees the same mailbox. See our IMAP versus POP3 article for the difference.

Step 5: test before you announce

1. Send a message from your new address to a personal account at a large provider and check where it lands.
2. Reply to it, and confirm the reply arrives in your new mailbox.
3. Look at the headers of the received message. You want to see SPF, DKIM and DMARC all passing.
4. Send to a second provider as well, since filtering varies.
5. Test from your phone on mobile data, to confirm your outgoing port is not blocked on your home network.

If anything fails, check the basics first: a typo in the MX target, a missing dot at the end of a hostname when your DNS editor requires it, or a leftover record from an earlier provider.

Step 6: finish the housekeeping

• Update your website contact page, invoices, email signatures and social profiles.
• Set up forwarding from the old address for a transition period.
• Agree on a mailbox size limit and an archiving habit, so nobody runs out of space unexpectedly.
• Write down where the DNS records live and who can change them.

If something does not work

Work from the outside in. Check that the MX record resolves to the right hostname, that the hostname resolves to an IP address, and that the mail server accepts the login. Most first-day problems are a wrong password, a wrong port, or a client that still has the old server saved. Writing down what you changed and when makes it much easier for support to help you.

Common mistakes to avoid

• Publishing two SPF records instead of one combined record.
• Pointing an MX record at an IP address instead of a hostname. MX targets must be hostnames.
• Forgetting that a CNAME cannot coexist with an MX record on the same name.
• Switching MX records before old mail has been copied across.

Business email with Zebra Hosting

With a Zebra Hosting email plan, mailboxes are set up automatically within minutes of payment and managed through Plesk, so the steps above are quick to follow. If you need to bring existing mail across, the team handles that migration for free. Take a look at the email hosting plans, or ask in the knowledge base if a step is unclear.