GoDaddy Email email configuration guide
GoDaddy Email: MX gateway before provider
Document a filtering gateway before the provider instead of treating it as a conflict. Start with the exact domain, subdomain, and provider account that owns the route.
A provider configuration symptom may look like:
MX gateway before provider after a provider configuration change.
A gateway changes the expected MX pattern
If a filtering service receives mail first, public MX should point to that gateway. The gateway must then relay accepted mail to the GoDaddy destination specified privately by the gateway setup.
- Confirm the gateway subscription and protected domain.
- Verify every public MX target belongs to that gateway.
- Check the gateway’s downstream GoDaddy route without exposing an unsupported direct path.
- Review logs on both systems for one test message.
- Remove mixed direct MX only when the gateway vendor requires it.
MailFixIt reports the mixed public set as context. It cannot inspect private gateway routing.
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.