How to Create MX Record in DNS Server A Step by Step Guide

Yes, you can create an MX record in a DNS server by following these steps. This guide covers what MX records are, why they matter for email, prerequisites, a practical step-by-step process for popular DNS platforms, testing and verification, and best practices to keep your mail delivery reliable. You’ll find concise, reader-friendly explanations, real-world tips, and quick checks you can run to ensure your setup is solid. This post uses a mix of listicles, checklists, and example configurations to help you implement with confidence.

Useful URLs and Resources:

Cloudflare MX Records – cloudflare.com
AWS Route 53 – aws.amazon.com/route53
Google Cloud DNS – cloud.google.com/dns
Microsoft DNS Manager – docs.microsoft.com
RFC 5321: SMTP – ietf.org
SPF, DKIM, DMARC guides – dmarc.org
MX record testing tools – mxtoolbox.com
DNS basics – cloudflare.com/learning/dns/

Introduction
Yes, you can create an MX record in a DNS server by following these steps. In this article, you’ll get a concise, practical, step-by-step approach to configuring MX records, plus tips on testing and troubleshooting. Here’s what you’ll learn:

What an MX record does and why it’s critical for email delivery
The prerequisites you need before creating MX records
A clear, provider-agnostic step-by-step guide, plus provider-specific how-tos for Cloudflare, AWS Route 53, Google Cloud DNS, and traditional BIND
How to test your MX records using common tools like dig and nslookup
Best practices for priorities, TTLs, and mail server naming
How to integrate MX configuration with SPF, DKIM, and DMARC for better deliverability
Common mistakes and quick fixes to avoid mail delivery problems

What is an MX Record and Why It Matters

An MX Mail Exchange record tells the internet which mail servers are responsible for accepting email for your domain.
Each MX entry has two parts: the domain name of the mail server the “mail exchanger” and a priority value. Lower numbers mean higher priority. If the highest-priority server isn’t available, mail is redirected to the next lowest-priority server.
You can have multiple MX records for redundancy. A typical setup includes at least two MX records pointing to different mail servers.
Practical impact: misconfigured MX records can halt inbound email or route it to the wrong server, causing missed messages, bouncebacks, or security concerns.

Prerequisites and Quick Checks

You own the domain and have access to your DNS hosting provider or hosting environment with DNS management rights.
You have a hostname that will handle mail, e.g., mail.yourdomain.com, mx1.yourdomain.com, etc. This hostname should have an A or AAAA record resolving to an IP address.
You know what your mail provider instructs for MX settings priority values and target hostnames. If you’re running your own mail server, you’ll configure the MX to point to that server.
A heads-up on TTL: start with a moderate TTL e.g., 300 seconds during testing so changes propagate faster, then consider longer TTLs e.g., 3600 seconds for production stability.
If you’re using SPF/DKIM/DMARC, plan to configure them alongside MX records for best deliverability.

Step-by-Step Guide: Create MX Record General Process

Prepare your mail exchanger hostname

Pick a hostname for your mail server, such as mail.yourdomain.com or mx.yourdomain.com.
Ensure there is a corresponding A IPv4 or AAAA IPv6 record for that hostname that points to the correct mail server IP address.
If you’re using a hosted mail service like Google Workspace, Microsoft 365, or Zoho, you’ll typically get a hostname to use e.g., aspmx.l.google.com. Make sure that hostname is resolvable.

Decide MX priority values

Plan to have at least two MX records with distinct priorities, e.g., 10 and 20.
Lower numeric value = higher priority. If the primary server is unavailable, mail is delivered to the next one.
Keep an eye on load balancing and failover expectations. Don’t set all priorities to the same value unless you explicitly want equal preference.

Add MX records to your DNS zone

In your DNS provider’s dashboard, find your domain’s DNS management page.
Add a new DNS record:
- Type: MX
- Name/Host: @ represents the root domain or your domain name
- Mail server / Value: the mail exchanger hostname e.g., mail.yourdomain.com.
- Priority: an integer e.g., 10
- TTL: choose an appropriate value start with 300 seconds for testing
Save or Apply the record.

Create or verify the corresponding A/AAAA record

If you used mail.yourdomain.com, ensure you have an A or AAAA record that resolves mail.yourdomain.com to your mail server’s IP address.
If you’re using a hosted mail service, this step may be unnecessary because the service provides its own mail exchanger hostnames with their own DNS records. still, you should ensure the hostnames they require exist and resolve properly.

Add second MX record for redundancy

Repeat the steps with a different mail server address e.g., mx2.yourdomain.com and a higher priority value e.g., 20.
Ensure the second hostname also has a resolvable A/AAAA record or is provided by your mail service.

Validate DNS propagation

After saving, check with a DNS query tool to confirm the MX records are published.
Use commands like:
- dig MX yourdomain.com
- nslookup -type=MX yourdomain.com
You should see one or more MX records with the hostnames and their priorities.

Test mail delivery

Send test emails to and from your domain to confirm inbound delivery.
If possible, monitor mail logs on your mail server to verify accepted connections and delivery attempts.
If you use a third-party mail service, verify inbound routing configuration in that service as well.

Provider-Specific Quickstart: Cloudflare, Route 53, Google Cloud DNS, and BIND

Cloudflare DNS management
- Open the Cloudflare dashboard, select your domain, go to DNS.
- Add Record → Type: MX, Name: @, Content: mail.yourdomain.com, Priority: 10, TTL: Auto or 300.
- Ensure an A/AAAA record exists for mail.yourdomain.com.
- Cloudflare’s proxy status orange cloud should be OFF for mail-related records. set to DNS only gray cloud to avoid breaking mail delivery.
AWS Route 53
- Open the Route 53 console, choose Hosted zones, select your domain.
- Create Record Set → Type: MX, Name: blank root domain or your subdomain, Value: “10 mail.yourdomain.com.” the trailing dot matters in some cases.
- Add a second MX with a different priority, e.g., “20 mail2.yourdomain.com.”
- Ensure the mail hostnames resolve with A/AAAA records.
Google Cloud DNS
- In the Google Cloud Console, go to Networking > Cloud DNS.
- Create a New Record Set → Type: MX, DNS Name: yourdomain.com., TTL: 300, Data: “10 mail.yourdomain.com.”
- Add additional MX with “20 mail2.yourdomain.com.” and ensure the hostnames have A/AAAA records.
BIND / Manual DNS
- In your zone file for your domain e.g., db.yourdomain, add lines such as:
  - @ IN MX 10 mail.yourdomain.com.
  - @ IN MX 20 mx2.yourdomain.com.
  - mail.yourdomain.com. IN A 203.0.113.10
  - mx2.yourdomain.com. IN A 203.0.113.20
- Reload or restart named to apply changes.

MX Records: Tables, Formats, and Examples

Typical MX record format DNS zone syntax:
- domain.com. IN MX priority mail exchanger.
- Example:
  - yourdomain.com. IN MX 10 mail.yourdomain.com.
  - yourdomain.com. IN MX 20 mail2.yourdomain.com.
Primary vs. secondary: Primary is the lowest numeric value. you can have multiple secondaries for redundancy.
A/AAAA requirement: Ensure mail.yourdomain.com resolves to a live mail server IP. Without this, mail won’t be delivered properly.

Common Pitfalls and How to Avoid Them

Missing A/AAAA for mail hostname: Always create or verify the A/AAAA record for the MX target.
Wrong trailing dot in zone files: In some DNS servers, the mail host may need a trailing dot mail.yourdomain.com. to indicate a fully qualified domain name.
Incorrect TTL during testing: Very long TTLs can slow propagation after changes. use a shorter TTL during testing.
Using the same hostname for MX entries: If all MX entries point to the same host that’s not properly configured, you won’t have proper failover.
Overlapping policies with SPF/DKIM/DMARC: Ensure these records align with your mail flow. misconfiguration can impact deliverability.
Not testing externally: Internal DNS checks aren’t enough—test from outside networks to see what external mail servers see.

Testing and Verification: Quick Methods

DNS MX lookup
- You should see one or more lines with priorities and hostnames, e.g., 10 mail.yourdomain.com.
Resolve MX targets
- dig mail.yourdomain.com A
- dig mail.yourdomain.com AAAA if you use IPv6
Mail delivery test
- Send a test email from an external account and verify receipt in the inbox and mail logs.
Verify email routing
- If you use a hosted service, check the service’s inbound mail flow page or logs to confirm it’s accepting mail for your domain.
Propagation check
- Because DNS caches may exist, allow up to 24-48 hours for full propagation, though changes usually propagate faster with shorter TTLs.

Table: Example MX Setup Scenarios

Scenario 1: Simple single primary with fallback
- Priority 10: mail.yourdomain.com
- Priority 20: mail2.yourdomain.com
- mail.yourdomain.com A record: 203.0.113.10
- mail2.yourdomain.com A record: 203.0.113.11
Scenario 2: Hosted mail service Google Workspace
- Priority 1: ASPMX.L.GOOGLE.COM
- Priority 5: ALT1.ASPMX.L.GOOGLE.COM
- Priority 5: ALT2.ASPMX.LGOOGLE.COM
- Priority 10: ASPMX.L.GOOGLE.COM backup
- Ensure the corresponding MX target hostnames are resolvable and are managed by Google’s infrastructure.

Best Practices for Reliability and Deliverability

Keep at least two MX records with different priorities for redundancy.
Use meaningful, stable hostnames for MX targets. avoid dynamic or frequently changing endpoints.
Ensure the MX targets have reliable reverse DNS PTR records pointing back to the mail server, as many mail systems perform PTR checks during mail delivery.
Align MX with SPF, DKIM, and DMARC:
- SPF: Publish an SPF record that authorizes your mail sending sources.
- DKIM: Configure DKIM signing with your mail provider or mail server.
- DMARC: Publish DMARC policy to specify how to handle unauthenticated mail.
Monitor deliverability metrics:
- Keep an eye on bounce rates, spam reports, and DMARC alignment to catch issues early.
Document changes:
- Maintain internal change logs for DNS changes related to MX records and mail routing.
Regular audits:
- Periodically check that MX records still point to valid mail exchangers, especially after DNS provider changes or service migrations.

Security Considerations

Do not expose mail servers to public networks without proper security controls.
Enforce TLS for SMTP when possible STARTTLS to protect mail in transit.
Regularly rotate credentials if you operate your own mail server and monitor for unusual mail activity.

FAQ Section

Table of Contents

Frequently Asked Questions

What is an MX record?

An MX record specifies the mail servers responsible for receiving emails for a domain and their priority.

How many MX records should I have?

Typically two or more to provide redundancy. at least one primary and one secondary.

What is the difference between priority values?

Lower numbers have higher priority. If the primary is unavailable, delivery moves to the next highest-priority server.

How do I know my MX record is configured correctly?

Use MX lookup tools dig or nslookup to confirm the MX entries exist and point to resolvable hosts. Also test with an actual email flow.

Can I use the same mail server for both MX records?

You can, but it defeats redundancy. If that server goes down, mail delivery fails. Use different servers or providers for redundancy. The Shocking Truth About Leaving a Discord Server and What You Need to Know

Do MX records require an A/AAAA record?

Yes. The mail exchanger host MX target must resolve to an IP via A IPv4 or AAAA IPv6.

How do I test MX records on Windows?

Use nslookup:

nslookup
set type=MX
yourdomain.com

How do I test MX records on macOS/Linux?

Use dig:

dig MX yourdomain.com

What happens if there is no MX record?

Some mail servers will still attempt to deliver to an A/AAAA record, but most will consider the domain invalid for email, resulting in bounce or rejection.

Should I configure DKIM/DMARC after MX setup?

Yes. MX only handles delivery routing. DKIM and DMARC help with authentication and deliverability. Connect to Microsoft Exchange Server on iPhone Step by Step Guide: Setup, AutoDiscover, Email, Outlook App

How long does DNS propagation take after changing MX records?

Propagation can take from a few minutes to up to 48 hours, depending on TTL settings and DNS caching.

What TTL should I use for MX records?

During testing, 300 seconds is common for quick propagation. In production, many domains use 3600 seconds or longer for stability.

Can I point MX records to a hostname hosted elsewhere e.g., a third-party mail service?

Yes. Just ensure the hostname resolves to the correct mail servers and that the service requires you to point to their MX names.

What if my mail provider gives me multiple MX targets with different priorities?

Follow their guidance. Typically you’ll replicate the priority values they provide and ensure DNS hostnames resolve to the provider’s mail servers.

How often should I review MX records?

Do a quarterly check or anytime you migrate email providers, update IPs, or change mail routing. How to Fix the DNS Server Isn’t Responding Error

Final Notes

A well-implemented MX setup is foundational for reliable email delivery. Take the time to configure both primary and secondary MX records, verify the A/AAAA records for the mail exchangers, and test thoroughly using external queries and actual mail tests.
Don’t forget to align with SPF, DKIM, and DMARC to improve deliverability and protect your domain from spoofing.
If you run into issues, check DNS propagation status, verify that there are no syntax errors in zone files, and consult your mail provider’s specific MX guidance. With careful setup and regular checks, your domain will handle mail smoothly and securely.

Sources:

如何安装v2ray全流程图解：在VPN场景下的实现与注意事项

机场vpn ⭐ github：在机场环境下稳定访问 GitHub 的完整指南、VPN 选择与设置、速度优化与隐私保护

九工大 vpn接続方法全面指南：校园网远程访问、设置要点、常见问题与安全要点

2025年中国大陆地区稳定好用的vpn节点选择指南 How To Execute A Job In SQL Server Like A Pro A Step By Step Guide

蚂蚁加速器破解版：使用风险与合法替代方案的完整对比指南