GoDaddy Email email configuration guide

GoDaddy Email: Mailbox migration routing

Plan coexistence, priorities, and cutover evidence during provider migration. Start with the exact domain, subdomain, and provider account that owns the route.

Problem description

A provider configuration symptom may look like:

Mailbox migration routing after a provider configuration change.

Plan the cutover

Create destination mailboxes and copy data before changing MX. Lower the MX TTL in advance when possible, and record the old values for rollback.

  1. Confirm every mailbox, alias, group, and forwarding rule at the new provider.
  2. Configure SPF and DKIM for the new sending path before use.
  3. Replace MX with one provider’s complete supported set; do not invent mixed priority routing.
  4. Keep the old service available while cached MX answers expire.
  5. Test inbound and outbound mail, then retire the old route.

MailFixIt checks public routing and authentication. It cannot verify mailbox contents or private migration state.

Frequently asked questions

What does MailFixIt check for GoDaddy Email?

It helps compare public DNS evidence with the provider setup path. It does not access the provider account or claim that a DNS result alone proves sending or receiving.

Should I replace all existing DNS records with provider values?

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

Related email diagnostics

Primary sources: GoDaddy Email official setup guidance.