How to Add and Manage Mail Exchange Records in GoDaddy

Configuring Mail Exchange (MX) records on your GoDaddy domain tells the global Domain Name System (DNS) which email servers are authorized to receive messages on your behalf. Whether you are migrating to a hosted provider like Google Workspace or setting up a self-hosted mail server, getting your DNS routing right is essential to avoid bounced messages and lost communications.

Before you start making changes to your DNS zone file, it is wise to verify your current email routing setup using the MX Lookup tool on XiaTools to see existing records and prevent delivery conflicts.

Understanding MX Record Components

An MX record consists of a few specific parts that must be entered correctly into your DNS manager. If any single character is out of place, inbound mail will fail instantly.

Host, Priority, and Destination Values

When you add or edit an MX entry, GoDaddy asks for three primary values:

• Type: Always set to MX.
• Name (or Host): Usually denoted by @ to represent your root domain (e.g., example.com), or a subdomain like mail if required by your provider.
• Priority: An integer value (such as 0, 10, or 50) that determines the order of preference for your mail servers. Lower numbers mean higher priority.
• Points to (or Destination/Value): The fully qualified domain name (FQDN) of the mail server provided by your email host.
• TTL (Time to Live): How long resolvers cache the record. GoDaddy defaults to 1 hour, which is standard for updates.

Step-by-Step GoDaddy MX Record Configuration

Updating your DNS zone in GoDaddy is straightforward, but the interface requires precision. Follow these steps to add your provider's specific mail routing settings.

1. Log in to your GoDaddy account and navigate to your My Products page.
2. Scroll down to Domains and click the three dots or the settings gear next to the domain you want to update, then select Manage DNS.
3. Look at your existing DNS records. If you see old MX records pointing to GoDaddy Workspace or another provider, you will need to delete them or edit them to match your new provider.
4. Click the Add New Record button at the bottom of the DNS records table.
5. Select MX from the Type dropdown menu.
6. In the Name field, enter @ for your root domain.
7. In the Priority field, enter the preference number specified by your email provider (for example, 1 or 10).
8. In the Points to field, enter the destination mail server address (for example, mail.example.com or smtp.google.com).
9. Leave the TTL at the default setting (1 Hour) unless instructed otherwise.
10. Click Save to apply the changes.

Repeat this process if your email provider requires multiple backup or secondary MX records with higher priority numbers (such as 20 or 30).

Provider-Specific Examples

Different email hosting platforms require exact syntax to function properly. Here is how standard configurations look for major enterprise mail providers.

Google Workspace Example

Google Workspace requires a primary record and four backup records. When adding these in GoDaddy, set the Name to @ for all of them.

Type	Name	Priority	Points to	TTL
MX	@	1	SMTP.GOOGLE.COM	1 Hour
MX	@	5	ALT1.ASPMX.L.GOOGLE.COM	1 Hour
MX	@	5	ALT2.ASPMX.L.GOOGLE.COM	1 Hour
MX	@	10	ALT3.ASPMX.L.GOOGLE.COM	1 Hour
MX	@	10	ALT4.ASPMX.L.GOOGLE.COM	1 Hour

Microsoft 365 Example

Microsoft 365 typically uses a single MX record mapped specifically to your tenant domain name.

Type: MX
Name: @
Priority: 0
Points to: example-com.mail.protection.outlook.com
TTL: 1 Hour

Verifying Your DNS Changes

Once your godaddy mx record configuration is saved, DNS propagation takes anywhere from a few minutes to a few hours globally. You can verify that your records are active from your command line using diagnostic utilities.

Using nslookup on Windows or Linux

Open your terminal or PowerShell window and query the MX records for your domain:

nslookup -type=MX example.com

Sample output:

Server:  dns.google
Address: 8.8.8.8

Non-authoritative answer:
example.com     MX preference = 1, mail exchanger = smtp.google.com
example.com     MX preference = 5, mail exchanger = alt1.aspmx.l.google.com

Using dig on Linux or macOS

dig example.com MX +short

Sample output:

1 smtp.google.com.
5 alt1.aspmx.l.google.com.

If the output reflects your newly added servers, your configuration is live and propagating correctly.

Common Mistakes and How to Fix Them

• Conflicting Default Records: GoDaddy often pre-populates default MX records pointing to their own internal mail servers. Failing to delete these old records causes email delivery to split or fail completely.
• Missing Trailing Dots: While GoDaddy automatically manages trailing dots on fully qualified domain names, pasting a destination with a trailing dot into other registrars can break routing. Always double-check your provider's formatting guidelines.
• Incorrect Priority Numbers: Entering a high number when the provider requested a primary low number causes mail servers to bypass your primary inbox.
• Forgetting SPF and DKIM: MX records only route inbound mail. Remember to also configure your SPF (TXT) and DKIM records to ensure outbound deliverability and prevent spam classification.

Quick Checklist for MX Record Success

• Checked existing records to prevent conflicts
• Deleted old or obsolete GoDaddy default MX entries
• Entered @ for the root domain host field
• Assigned correct priority integers provided by the mail host
• Verified propagation using command-line tools or online lookups