Configure Your Domain for Email Hosting & Testing

Using a professional email address such as sales@yourcompany.com can strengthen your brand, build customer trust, and make business communication more consistent.

However, purchasing an email hosting service is only the first step. Your domain must also be configured correctly so that emails can be sent, received, and authenticated reliably.

Incorrect DNS settings may cause messages to:

• Fail to reach the recipient
• Be rejected by receiving mail servers
• Land in the spam or junk folder
• Fail SPF, DKIM, or DMARC authentication
• Be impersonated by unauthorized senders

In this guide, Việt SEO explains how to configure a domain for email hosting, verify the essential DNS records, test email deliverability, and identify common setup problems.

What Is Email Hosting?

Email hosting is a service that stores, sends, receives, and manages email accounts associated with a business domain.

Instead of using a free address such as:

yourcompany@gmail.com

a business can use its own domain:

contact@yourcompany.com
sales@yourcompany.com
support@yourcompany.com

This creates a more professional and consistent identity across customer service, sales, recruitment, accounting, and internal communication.

Email hosting can be provided through:

• A dedicated business email hosting provider
• A website hosting control panel
• Google Workspace
• Microsoft 365
• Zoho Mail
• A privately managed mail server

Regardless of the provider, the domain’s DNS records must be configured according to the email service’s instructions.

Benefits of Business Email Hosting

1. A More Professional Brand Image

An email address that matches your company’s domain helps customers recognize the sender and increases confidence in the legitimacy of the message.

For example:

sales@yourcompany.com

usually appears more professional than an address created through a free personal email platform.

2. Centralized Email Management

Administrators can create, suspend, rename, or remove employee accounts as the organization changes.

This helps businesses maintain control over corporate communication instead of relying on personal email accounts owned by individual employees.

3. Improved Email Authentication

Business email systems can be configured with SPF, DKIM, and DMARC. These records help receiving servers verify that a message genuinely comes from an authorized source.

4. Better Security and Spam Filtering

Depending on the provider and service package, business email hosting may include:

• Spam filtering
• Malware and virus scanning
• Login protection
• Two-factor authentication
• Email backups
• Sending and receiving logs

5. Scalability for Growing Businesses

Businesses can add more mailboxes, increase storage, or upgrade their service as the number of employees and email volume grows.

What You Need Before Configuring Email Hosting

Before changing any DNS records, prepare the following information:

• Access to the domain’s DNS management panel
• The MX records supplied by the email provider
• The SPF value supplied by the provider
• The DKIM selector and public key
• The recommended DMARC configuration
• The hostname used for webmail, IMAP, POP3, and SMTP
• The required ports and encryption methods

DNS may be managed by the domain registrar, hosting company, Cloudflare, or another DNS provider. Make sure you edit the records in the platform that currently manages the domain’s authoritative nameservers.

Essential DNS Records for Email Hosting

Most business email systems require four main DNS components:

• MX for receiving email
• SPF for authorizing sending servers
• DKIM for digitally signing email
• DMARC for defining authentication policy and reporting

Some providers may also require A, CNAME, or autodiscover records.

1. MX Record

An MX record tells other mail servers where messages for your domain should be delivered.

Without a valid MX record, your domain may be unable to receive email.

A typical MX configuration may look like this:

Type: MX
Host: @
Destination: mail.yourdomain.com
Priority: 10

However, you must use the exact MX destination provided by your email hosting company.

For example, a hosted email platform may provide several MX records:

Priority 10: mx1.emailprovider.com
Priority 20: mx2.emailprovider.com

The lower number represents the higher delivery priority. If the first server is unavailable, the sending system may attempt delivery through the next MX server.

Important MX Record Notes

• Do not point the MX record to an IP address unless your provider specifically requires it.
• Remove old MX records when migrating to a new email provider unless they are still required.
• Do not combine MX records from unrelated email platforms.
• Check whether the DNS panel automatically adds your domain name to the hostname.

2. Mail Hostname Record

If the MX record points to a hostname such as mail.yourdomain.com, that hostname normally needs an A record pointing to the mail server’s IP address.

Example:

Type: A
Host: mail
Value: 203.0.113.10

When using a third-party hosted platform, the provider may instead request a CNAME record or provide an external MX hostname that does not require an A record on your domain.

Follow the provider’s configuration rather than creating records based only on generic examples.

3. SPF Record

SPF stands for Sender Policy Framework. It identifies which servers are authorized to send email on behalf of a domain.

SPF is published as a TXT record at the root domain.

Example:

Type: TXT
Host: @
Value: v=spf1 include:spf.emailprovider.com ~all

The exact value depends on the systems that send email for your business.

These may include:

• Your business email hosting provider
• A website contact form
• A CRM platform
• An invoicing system
• An email marketing service
• A help desk platform

Avoid Creating Multiple SPF Records

A domain should normally have only one SPF record.

If several services are authorized to send email, their mechanisms should be combined into a single SPF value.

Incorrect example:

v=spf1 include:provider-one.com ~all
v=spf1 include:provider-two.com ~all

Combined example:

v=spf1 include:provider-one.com include:provider-two.com ~all

Always confirm the final value with your email or DNS administrator, especially when multiple platforms send email for the same domain.

Understanding SPF “all” Mechanisms

• ~all: Soft fail. Unauthorized sources may still be accepted but treated with suspicion.
• -all: Hard fail. The domain states that unauthorized sources should fail SPF.
• ?all: Neutral. The domain does not make a clear authorization statement.

A stricter policy should only be used after all legitimate sending services have been identified.

4. DKIM Record

DKIM stands for DomainKeys Identified Mail. It adds a cryptographic signature to outgoing messages.

The receiving server can compare this signature with the public key published in DNS. This helps confirm that:

• The message was sent through an authorized system
• The signed parts of the message were not modified during delivery

A DKIM record is usually published as a TXT or CNAME record at a hostname containing a selector.

Example:

Type: TXT
Host: default._domainkey
Value: v=DKIM1; k=rsa; p=MIGfMA0GCSq...

The selector may be named:

• default
• mail
• selector1
• google
• Another custom value supplied by the provider

Do not create your own DKIM value unless you manage the mail server and understand the required private and public key configuration.

Common DKIM Configuration Errors

• Using the wrong selector
• Adding the full domain when the DNS provider already appends it
• Breaking or truncating the public key
• Publishing the key but not enabling DKIM signing on the mail server
• Leaving an obsolete DKIM record after changing providers

5. DMARC Record

DMARC stands for Domain-based Message Authentication, Reporting and Conformance.

DMARC uses SPF and DKIM results to help domain owners:

• Define how unauthenticated email should be handled
• Receive reports about authentication activity
• Reduce domain spoofing and impersonation

A basic monitoring record may look like this:

Type: TXT
Host: _dmarc
Value: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Common DMARC policies include:

• p=none: Monitor authentication without requesting enforcement.
• p=quarantine: Ask receiving servers to treat failing messages as suspicious.
• p=reject: Ask receiving servers to reject messages that fail DMARC.

A more restrictive policy should normally be introduced gradually after reviewing reports and confirming that all legitimate email sources are correctly authenticated.

What Is DMARC Alignment?

DMARC does not simply check whether SPF or DKIM passes. It also checks whether the authenticated domain aligns with the domain visible in the email’s From address.

This is why an SPF or DKIM result may pass while DMARC still fails.

6. Autodiscover and Email Client Records

Some email platforms use CNAME or SRV records to help applications such as Outlook automatically detect mailbox settings.

Example:

Type: CNAME
Host: autodiscover
Value: autodiscover.emailprovider.com

The exact hostname varies by provider. Only add the record when it is included in the official configuration instructions.

How to Configure Your Domain for Email Hosting

Step 1: Identify Your DNS Provider

Log in to the platform that manages your DNS records.

This may be:

• Your domain registrar
• Your web hosting control panel
• Cloudflare
• A separate DNS management provider

If you are unsure, check the domain’s current nameservers or ask your hosting provider.

Step 2: Back Up Existing DNS Records

Before making changes, save a copy or screenshot of the existing DNS zone.

This is especially important when migrating from another email provider because removing the wrong record could affect:

• The website
• Email delivery
• Subdomains
• Verification services
• Third-party platforms

Step 3: Add or Update the MX Records

Delete obsolete MX records and add the records supplied by the new email provider.

Check the following carefully:

• Host or name
• Mail server destination
• Priority
• TTL

Step 4: Configure SPF

Check whether the domain already has an SPF TXT record.

If it does, update the existing value instead of creating a second SPF record. Include every legitimate platform that sends email using your domain.

Step 5: Publish and Enable DKIM

Add the DKIM record supplied by the email provider. After DNS propagation, return to the provider’s administration panel and activate DKIM signing if a separate activation step is required.

Step 6: Configure DMARC

Start with a monitoring policy when the domain has multiple or uncertain sending sources.

Review the reports, correct authentication problems, and then consider moving toward quarantine or reject.

Step 7: Add Required Supporting Records

Depending on the provider, you may also need records for:

• Mail hostname
• Autodiscover
• Webmail
• Domain verification
• Service-specific routing

Step 8: Create and Test the Mailboxes

Create at least one test mailbox and confirm that it can:

• Send email to an external address
• Receive email from an external address
• Reply successfully
• Connect through webmail
• Connect through the required email applications

How Long Do DNS Changes Take?

DNS changes are not always visible immediately.

Propagation time depends on:

• The TTL of the previous record
• The DNS provider
• Resolver caching
• The type of record being changed

Some changes may appear within minutes, while others can take several hours. In certain situations, cached results may remain visible for up to 24–48 hours.

During a mail migration, some messages may temporarily be delivered according to old cached MX information. For this reason, businesses should keep the previous email system active during the transition whenever possible.

How to Check Email DNS Records

After configuring DNS, verify each record independently.

Check MX Records

An MX lookup should show the mail servers supplied by your email hosting provider.

Confirm that:

• No obsolete MX records remain
• The priorities are correct
• The destinations resolve properly

Check SPF

Verify that the domain publishes only one SPF record and that the required sending services are included.

Also check whether the SPF configuration exceeds DNS lookup limits, which can cause authentication errors.

Check DKIM

Use the exact selector supplied by your provider.

For example, if the selector is default, the lookup hostname is normally:

default._domainkey.yourdomain.com

A successful DNS lookup confirms that the public record exists. You should also send a test message to verify that outgoing mail is actually being signed.

Check DMARC

Verify that the record exists at:

_dmarc.yourdomain.com

Confirm that the syntax is valid and that the reporting mailbox can receive messages.

How to Test Email Delivery

Correct DNS records are essential, but they do not guarantee that every message will reach the inbox. Deliverability also depends on sending reputation, server configuration, message content, volume, and recipient engagement.

1. Send and Receive Basic Test Messages

Send messages between the business mailbox and several external providers.

For example:

• Gmail
• Outlook or Hotmail
• Yahoo Mail
• Another corporate domain

Confirm whether each message:

• Arrives successfully
• Lands in the inbox or spam folder
• Displays the correct sender name
• Can be replied to
• Contains working links and attachments

2. Check Message Authentication Results

Open the original message headers in the receiving mailbox and review:

• SPF result
• DKIM result
• DMARC result
• Return-Path
• From domain
• Sending IP

Ideally, legitimate business messages should show successful authentication and appropriate domain alignment.

3. Test with Mail-Tester

Mail-Tester can provide a quick review of:

• SPF
• DKIM
• DMARC
• Sending IP reputation
• Blacklist status
• Message structure and content

How to Use Mail-Tester

1. Open the Mail-Tester website.
2. Copy the temporary test email address displayed on the page.
3. Send a normal business email from the account you want to test.
4. Return to the website and view the report.
5. Review each warning rather than focusing only on the total score.

A high score is useful, but it does not guarantee inbox placement. The report should be used as a diagnostic reference.

4. Verify the DKIM Selector

Use a DKIM lookup tool and enter:

• The domain name
• The DKIM selector

If the public key appears, the DNS record has been published. If the record is missing, confirm the selector, hostname format, and DNS provider.

5. Check IP and Domain Reputation

Review whether the sending IP or domain appears on major email blocklists.

A listing does not always mean all email will fail, but it may indicate:

• Compromised email accounts
• Malware or spam activity
• Poor shared-server reputation
• Uncontrolled bulk sending
• Incorrect server configuration

Common Email Hosting Configuration Errors

1. Incorrect or Obsolete MX Records

Old MX records can route incoming mail to the wrong platform. This is common after migrating between hosting providers.

2. Multiple SPF Records

Publishing more than one SPF record may cause SPF validation to return an error. Authorized senders should be combined into one valid policy.

3. DKIM Published but Not Enabled

A public key may exist in DNS while the outgoing server is not signing messages. DNS verification and real-message testing are both necessary.

4. A Strict DMARC Policy Applied Too Early

Using p=reject before identifying all legitimate sending systems may cause valid messages from websites, CRMs, or third-party platforms to be rejected.

5. Website Forms Send Through an Unauthenticated Server

Contact forms that use basic PHP mail functions or an unrelated server may fail SPF, DKIM, or DMARC.

Whenever possible, configure the website to send through authenticated SMTP or a suitable transactional email service.

6. Proxy Enabled for a Mail Hostname

If DNS is managed through Cloudflare, mail-related records generally should not be proxied through the standard web proxy.

Mail hostnames normally need to remain in DNS-only mode unless a specific supported mail service states otherwise.

7. Missing or Incorrect Reverse DNS

Organizations operating their own mail server should ensure that the sending IP has appropriate reverse DNS and that the server hostname is configured consistently.

This setting is usually controlled by the server or IP provider, not through the domain’s normal DNS zone.

8. Sending Large Volumes from a New Domain

New domains and sending IPs may not yet have an established reputation. Sending a large volume immediately can trigger filtering.

Increase sending gradually and focus on legitimate recipients who expect the messages.

Email Hosting Security Best Practices

• Use strong and unique passwords for every mailbox.
• Enable two-factor authentication when available.
• Disable or reset accounts belonging to former employees.
• Avoid sharing mailbox passwords through chat applications.
• Use encrypted IMAP and SMTP connections.
• Review login and sending logs for unusual activity.
• Keep email applications and devices updated.
• Train employees to recognize phishing and impersonation attempts.
• Back up important mailboxes according to business requirements.
• Limit bulk sending from normal employee mailboxes.

Business Email Hosting Services at Việt SEO

Việt SEO provides business email hosting solutions for companies that need professional domain-based email, reliable configuration, and technical support.

Our service is suitable for:

• Small and medium-sized businesses
• Sales and customer support teams
• Companies migrating from free email accounts
• Organizations requiring centralized mailbox management
• Businesses experiencing spam or delivery problems
• Companies that need support configuring email on multiple devices

Why Choose Email Hosting from Việt SEO?

1. Professional Email Addresses

Create email addresses associated with your company domain, such as:

sales@yourcompany.com
support@yourcompany.com
accounting@yourcompany.com

This helps establish a consistent identity across departments and customer touchpoints.

2. DNS and Authentication Configuration

Việt SEO can assist with configuring:

• MX records
• SPF
• DKIM
• DMARC
• Mail hostnames
• Webmail and email client settings

3. Access on Multiple Devices

Depending on the service package, mailboxes can be accessed through:

• Webmail
• Microsoft Outlook
• Desktop email software
• iPhone and iPad
• Android phones and tablets
• Applications supporting IMAP and SMTP

4. Spam and Malware Protection

Email filtering helps reduce unwanted or potentially dangerous messages before they reach the user’s inbox.

No filtering system can eliminate every threat, so businesses should combine technical protection with appropriate employee awareness and account security.

5. Migration and Setup Support

Việt SEO can support businesses when:

• Moving from another email provider
• Creating new employee accounts
• Configuring email on computers and mobile devices
• Troubleshooting delivery problems
• Correcting DNS authentication records

6. Technical Support

Our technical team can help diagnose common issues involving login, DNS records, receiving, sending, spam filtering, and email client configuration.

Request a Business Email Configuration Check

Are your business emails landing in spam? Are customers reporting that they cannot receive your messages? Are you unsure whether SPF, DKIM, and DMARC are configured correctly?

Việt SEO can help review your current email setup.

The diagnostic process may include:

• Checking MX records
• Reviewing SPF configuration
• Verifying DKIM publication
• Checking DMARC policy and syntax
• Reviewing common domain and IP reputation issues
• Testing basic email authentication
• Providing recommendations for configuration improvements

Please note that email inbox placement depends on many factors. A configuration check can identify technical issues, but no provider can guarantee that every message will always reach the primary inbox.

Việt SEO Contact Information

• Website: https://vietseo.com/
• Hotline/Zalo: 0917 212 969

Frequently Asked Questions About Email Hosting

Build a Reliable Business Email System

A professional email address is valuable only when the underlying system is configured correctly.

MX records determine where incoming messages are delivered. SPF identifies authorized senders. DKIM signs outgoing messages, while DMARC helps protect the visible From domain and provides authentication reporting.

Together with secure accounts, responsible sending practices, and regular monitoring, these records create a stronger foundation for reliable business communication.

If you need help configuring a new email system, migrating from another provider, or diagnosing email delivery problems, contact Việt SEO for technical support and a solution suitable for your business.