How to Set Up Business Email on a Custom Domain: The Complete Guide
Configure DNS, MX, SPF, DKIM & DMARC for 100% Inbox Deliverability
Written by Omar S. · Lead Email Systems Architect
Reviewed by Vexm Deliverability Team · Editorial standards verified
Key Takeaways
- ✓MX (Mail Exchange) records dictate which mail transfer agents receive incoming email for your domain.
- ✓SPF records authorize specific relay IP addresses to prevent spammers from spoofing your address.
- ✓DKIM adds a public-key cryptographic signature to the header of every outgoing message.
- ✓DMARC instructs receiving mail servers (Gmail, Outlook) how to handle messages that fail SPF or DKIM.
1. Why Professional Email Requires a Custom Domain
Emailing prospective clients or business partners from a generic @gmail.com or @yahoo.com address damages brand credibility before the recipient even opens your message. A custom domain email (such as [email protected]) creates instant trust and establishes ownership of your corporate communications.
To run email on your custom domain, you do not need expensive per-seat enterprise suites. Modern platforms like Vexm Business Email allow you to connect any registrar domain (Cloudflare (opens in a new tab), Namecheap (opens in a new tab), GoDaddy (opens in a new tab)) and route unlimited mailboxes through standard DNS records without paying per-seat fees—as detailed in our Flat-Rate vs. Per-Seat Email Pricing Guide.
2. Configuring MX Records (Mail Exchanger)
Under the IETF RFC 5321 (opens in a new tab) standard, the MX record informs DNS resolvers which mail servers are authoritative to receive incoming messages for your domain. When someone dispatches an email to [email protected], their mail transfer agent resolves the MX record for yourcompany.com.
Always specify a priority number. Lower numbers indicate higher precedence. When pairing with Vexm, set the primary inbound gateway to priority 10. For full parameter breakdowns, consult our Frequently Asked Questions on DNS Records.
; Primary MX Record for Vexm
@ IN MX 10 mx.vexm.app.3. Enforcing SPF (Sender Policy Framework)
Defined by IETF RFC 7208 (opens in a new tab), an SPF record is an authoritative TXT record published in your DNS zone that enumerates every IP address and hostname permitted to relay emails on behalf of your domain name. This cryptographic authorization stops malicious actors from impersonating your executives or support desk.
Under NIST SP 800-177 Email Security Guidelines (opens in a new tab), you should only publish one SPF record per domain. If you utilize multiple relay services alongside Vexm, combine them using the standard include: directive.
; Authoritative SPF TXT Record
@ IN TXT "v=spf1 include:_spf.vexm.app ~all"4. Cryptographic Signing with DKIM
DomainKeys Identified Mail (IETF RFC 6376 (opens in a new tab)) injects an asymmetric cryptographic signature into your message headers. When an outbound email is dispatched through Vexm, our mail server signs the payload with a private RSA key. The receiving mailbox provider verifies the header hash against the public key published in your DNS.
DKIM guarantees that the message originated from an authentic sender and was not altered in transit. Both Google Workspace Deliverability Guidelines (opens in a new tab) and Yahoo Mail require DKIM for primary inbox placement.
; DKIM Public Key Record (Selector: vexm)
vexm._domainkey IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD..."5. Adding DMARC for Policy Protection
DMARC (IETF RFC 7489 (opens in a new tab)) coordinates SPF and DKIM authentication into a unified policy statement. It instructs mailbox providers (Google, Microsoft Outlook, Apple iCloud) how to process incoming messages that fail authentication.
Begin with a monitoring policy (p=none) to review delivery reports (rua=) before upgrading to quarantine (p=quarantine) or strict rejection (p=reject). Once configured, you can test client connections with our IMAP & SMTP Setup Guide or explore Vexm Plans and Free Trial.
; DMARC Policy TXT Record
_dmarc IN TXT "v=DMARC1; p=none; sp=none; rua=mailto:[email protected];"Citations & Verification
Authoritative Standards & References
This technical guide cites authoritative RFC specifications, standards bodies, and official protocol documentation.
IETF RFC 5321: Simple Mail Transfer Protocol ↗
The core specification for internet message transmission and MX record mail routing.
IETF RFC 7208: Sender Policy Framework (SPF) ↗
Standard defining authorization mechanisms to prevent domain name forgery and spoofing.
IETF RFC 6376: DomainKeys Identified Mail (DKIM) Signatures ↗
Cryptographic specification for verifying message provenance and tamper-evident transit.
IETF RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC) ↗
Standard governing sender policy assertion, quarantine rules, and aggregate reporting.
NIST SP 800-177 Rev 1: Trustworthy Email Guidelines ↗
Federal recommendations for deploying modern cryptographic email authentication protocols.
Vexm Core Services & DNS Specification →
Technical manifest of Vexm MX, SPF, DKIM, and IMAP/SMTP endpoints.
Catch-All Mailbox Setup & Routing →
Guide to capturing mistyped customer inquiries with zero dropped incoming messages.
Q&A
Frequently Asked Questions
How long does DNS propagation take for MX, SPF, and DKIM records?+
Can I use multiple MX records on my custom domain?+
What happens if I do not set up DKIM and DMARC?+
Ready to implement this on your domain?
Vexm automates MX verification, SPF inclusion, and DKIM signing so your business email is live in three minutes.
Lead Email Systems Architect at Vexm
Specializing in high-throughput mail transfer agents, Dovecot IMAP storage clusters, and DKIM/DMARC authentication protocols. Overseeing mail delivery reliability and antispam defenses across Vexm's infrastructure.