Custom Domain Email Setup 2026 — A Step-by-Step Guide for Small Teams

Last updated: April 2026

Most small teams think they need Google Workspace or Microsoft 365 to get professional email on their own domain. They don't. Those products exist because enterprise customers need Vault eDiscovery, advanced DLP controls, and shared drives with complex permission matrices. If your team is 3 people or 30, you're paying for 80% of features you'll never open.

This guide walks through setting up a custom domain email (like [email protected]) for a small team — the focused version, with just what actually matters: sending, receiving, DNS records that don't land you in spam folders, and a setup that takes about 15 minutes start to finish.

Why a custom domain email matters

Using @gmail.com or @yahoo.com for business communication quietly costs you four things:

• Credibility. Clients read [email protected] as "real business." [email protected] reads as "side project." The perception gap is real and measurable.
• Brand consistency. Every outbound email is a brand impression. Your domain reinforces your name; a free mailbox provider dilutes it.
• Account continuity. If an employee leaves, you keep the address and the conversation history. With a personal Gmail account, both walk out the door.
• Deliverability. Properly-configured custom domains with SPF, DKIM, and DMARC get flagged as spam less often than free-mailbox accounts sending business email.

If any of that matters to your team, setting up custom domain email is worth the 15 minutes.

What you'll need before starting

• A domain you own, through any registrar (GoDaddy, Namecheap, Cloudflare Registrar, Hostinger, Google Domains — any of them work)
• Admin access to that domain's DNS settings (usually the same registrar, or Cloudflare if you've moved DNS there)
• A Roomie account on any plan that includes email
• About 15 minutes

No credit card verification walls, no identity checks, no international billing gymnastics.

Understanding the 4 DNS records you'll add

Before touching any UI, it helps to know what the records actually do. Every custom email setup uses the same four.

MX (Mail Exchanger)

Tells the world 'send email for @yourcompany.com to this mail server.' Without an MX record, no mail arrives.

SPF (Sender Policy Framework)

A TXT record that declares which servers are allowed to send email as @yourcompany.com. Stops spammers from spoofing your domain.

DKIM (DomainKeys Identified Mail)

A cryptographic signature on every outbound email. Receiving servers check it against a public key you publish in DNS. If the signature matches, the email is verified as authentically from you — not forged.

DMARC (Domain-based Message Authentication)

Tells receiving servers what to do if an email fails SPF or DKIM — reject it, quarantine it, or just report. Protects your domain from being impersonated in phishing attacks.

Roomie generates all four records for you. You just paste them into your DNS provider.

Step-by-step setup in Roomie

Step 1 — Open Mail Settings

Click the Mailbox icon in Roomie's left sidebar navigation.

Step 2 — Open the Domains panel

In Mailbox settings, click Domains. This is where you'll register the domain you want to receive email on.

Step 3 — Add your domain

Enter the domain you own (for example acmedesigns.com) and confirm. Roomie will create the workspace entry and generate the DNS records you need.

Step 4 — Copy the DNS records

Click your newly-added domain to reveal the four DNS records. You'll see MX, SPF, DKIM, and DMARC rows with the values pre-filled. Keep this tab open — you'll switch to Cloudflare next.

Step 5 — Paste the records into Cloudflare

If you use Cloudflare (most common):

1. Log in to dash.cloudflare.com.
2. Select your domain.
3. Go to DNS → Records.
4. Click Add record and create each of the four entries from Roomie: MX (name @, target from Roomie, priority 10), SPF (TXT, name @), DKIM (TXT or CNAME as Roomie specifies), DMARC (TXT, name _dmarc).
5. For each record, ensure Cloudflare's Proxy status is set to DNS only — gray cloud, not orange.

That last point matters. The orange cloud proxies HTTP traffic through Cloudflare, which breaks email delivery. Every email DNS record must be gray-clouded.

If you use a different DNS provider, the record content is identical everywhere — TXT, MX, and CNAME record types are internet standards. Common providers:

• GoDaddy: Dashboard → My Products → DNS → Manage → Add record
• Namecheap: Domain List → Manage → Advanced DNS → Add New Record
• Google Domains / Squarespace Domains: DNS → Custom records → Create new record
• Route53 (AWS): Hosted Zones → select domain → Create record
• Any other provider: look for 'Add DNS record', 'Manage DNS zone', or 'Custom DNS'. The four records you paste are the same in every case.

Step 6 — Wait for DNS to propagate

DNS propagation usually takes 5–30 minutes. On Cloudflare it is often under 5 minutes. Worst case (slower or older providers) can be up to 24 hours.

Back in Roomie, hit Refresh on the domain page. When all four records show as verified, you are ready to create mailboxes.

DNS propagation takes 5–30 minutes. If verification fails, wait 10 minutes and refresh.

Step 7 — Create email users

Navigate to Email Users, click Add Email User, enter the mailbox name (for example jane to create [email protected]), and assign it to a team member.

That user can now send and receive email at the new address — from the Roomie web app, the mobile app, or any IMAP-compatible client like Apple Mail or Thunderbird.

Troubleshooting common issues

DNS records won't verify

• Check for typos. Paste, don't retype. A single missing character in a DKIM key breaks the whole signature.
• TTL too high. Set to Auto or 300 seconds while you're still testing. Once verified, you can raise it.
• DNSSEC conflicts. If DNSSEC is enabled, temporarily disable it, verify the records, then re-enable.
• Cloudflare proxy on. Every email-related DNS record must be gray-cloud (DNS only), never orange-cloud (proxied). This is the #1 Cloudflare gotcha.

Emails landing in spam after verification

• Confirm both SPF and DKIM are verified in Roomie before sending real mail. Missing either is a near-guaranteed spam folder.
• Warm up new domains gradually. Send 20–50 emails per day for the first week. Sudden bulk sends from a brand-new domain trigger spam filters across Gmail, Outlook, and Yahoo.
• Avoid spammy subject lines on the first batch — no URGENT, no excessive punctuation, no all-caps.
• Start DMARC gently. A p=none (reporting-only) DMARC policy is safer than jumping straight to p=reject on day one.

"The domain is already in use" error

Someone on your team may have already added the domain. Check with your admin before re-adding.

When Roomie email is the right fit — and when it isn't

Roomie email is ideal if:

• You run a small-to-medium team (1–50 people)
• You need professional addresses on your own domain
• You want email integrated with your task board and chat, so threads can become tasks automatically
• You don't need enterprise-grade legal hold, eDiscovery, or complex shared-drive permission matrices

Roomie email is not the best fit if:

• You're in a regulated industry that requires specific compliance frameworks like HIPAA BAAs, FedRAMP, or government-grade data residency
• You run 500+ mailboxes with complex delegation hierarchies
• You're already deeply committed to Google Workspace for Google Sites, Google Groups, or enterprise Meet features

For those cases, Google Workspace or Microsoft 365 are appropriate. For most small and mid-sized teams, those platforms are overkill — you are paying for complexity you will not use.

Frequently asked questions

Can I use a .com.np or country-code domain?

Yes. Any valid domain works — .com, .org, .io, .com.np, .co.uk, anything with a real TLD and working DNS records.

Do I need to transfer my domain to Roomie?

No. Your domain stays where it is. Roomie just reads DNS records you add at your existing registrar.

Can I use my existing Gmail to send mail from my new custom address?

Roomie supports IMAP/SMTP for standard clients. You can configure Apple Mail, Outlook, or Thunderbird to send and receive through your Roomie mailbox. Gmail itself can also be configured to send-as a custom address via SMTP.

Will my old emails migrate over?

Migration from Gmail, Outlook, and IMAP-compatible providers is supported. Contact support if you'd like help setting up the import.

How long until emails actually work?

Usually 15–30 minutes from adding DNS records. Full worldwide propagation (worst case) can take 24 hours, but on Cloudflare it's typically under an hour.

What happens if I change DNS providers later?

Just recreate the same four records on the new provider. The record content stays identical. No changes needed inside Roomie.

Can I have multiple domains on one account?

Yes. Roomie supports multiple verified domains on the same workspace.

What about shared mailboxes like support@ or hello@?

Supported. Create them the same way as personal mailboxes, then give multiple team members access to the shared inbox.

Is there a size limit on attachments?

Up to 50MB per message. Larger files can be shared through Roomie's task and chat system without email attachments.

Does this replace my dedicated email client?

Optional. Roomie's web and mobile apps handle email natively with threaded conversations. You can also connect via IMAP if you prefer Apple Mail, Outlook, or Thunderbird.

Summary

Custom domain email is not complicated — four DNS records and about 15 minutes of patience while DNS propagates. Most of the complexity people associate with setting this up comes from vendors who bundle email with enterprise features small teams don't need.

If your team just wants professional email that works on your domain without the bloat, this setup is yours. Open Mailbox settings, add your domain, paste four records into Cloudflare, and you are done.

Questions or support needed? If you run into any issue in this setup, reach out to us at [email protected]