MailFixIt

GoDaddy Email email configuration guide

GoDaddy Email: MX records not receiving mail

Mail for the domain is not reaching GoDaddy Email, either because the public MX route is wrong or the destination account is not ready for the recipient.

Problem description

A provider setup symptom may look like:

MX records not receiving mail after a provider DNS change.

Check the sending domain

What this usually means

Mail for the domain is not reaching GoDaddy Email, either because the public MX route is wrong or the destination account is not ready for the recipient.

Fix it

  1. First identify the product shown in GoDaddy’s Email & Office Dashboard. Professional Email powered by Titan and Microsoft 365 use different MX records. The company that bills or registers the domain is not necessarily the mailbox provider.
  2. Confirm that the custom domain is verified and create every required mailbox, alias, or accepted domain before changing MX.
  3. Copy the complete MX set shown in the provider console for that exact domain.
  4. Replace obsolete MX records only if this provider should receive mail directly. If an intentional security gateway is public, configure its next hop instead.
  5. Check the public MX answer after cache expiry and send a new message to an address that exists.

Common mistake

MX records choose the receiving system; they do not create mailboxes. Mixing unrelated old and new provider MX records causes intermittent or rejected delivery.

What MailFixIt can check

MailFixIt can evaluate the public MX configuration and show missing, conflicting, or invalid DNS evidence. It cannot log in to GoDaddy Email or prove private account state.

Use the related guides for the exact DNS or authentication result. Test again after the provider has accepted the configuration.

Frequently asked questions

What does MailFixIt check for GoDaddy Email?

It checks the public MX record and visible conflicts. The provider console must confirm account activation, and a new message or delivery test must confirm the result.

Should I replace every existing DNS record with the provider values?

No. Confirm the exact record type and owner, preserve unrelated legitimate services, and change only the provider-controlled record required for the intended mail route.

Related email diagnostics

Email delivery delayed or rejected after a DNS migrationDiagnose email that stopped arriving after a DNS change. Compare public MX records with the intended provider and avoid false alarms for mail gateways. SPF is not configured for the envelope sender domainDiagnose SPF missing on a bounce or MAIL FROM subdomain. Check the exact envelope domain, add only authorized senders, and verify safely. DKIM public key record is invalid or revokedDiagnose an invalid or revoked DKIM public key record. Check the exact DKIM selector in public DNS before replacing a sender-provided key.

Primary sources: GoDaddy Professional Email DNS settings.