Fix Microsoft 365 email DNS in GoDaddy: when this repair path applies
Restore Exchange Online MX and SPF records in GoDaddy DNS, preserving any additional legitimate senders in the single SPF record. Use these steps when website works but Microsoft 365 mail fails, but first run the embedded diagnostic so the business-email DNS and mail authentication evidence supports this provider-specific path rather than a neighboring DNS, TLS, application or mail cause.
Find the authoritative setting before editing
GoDaddy DNS Management and the domain product that currently owns the authoritative nameservers. For Fix Microsoft 365 email DNS in GoDaddy, confirm the active nameservers and exact service owner before changing confirm active DNS is GoDaddy. A DNS-looking screen at godaddy has no public effect when another provider is authoritative for the zone.
Evidence to save for Fix Microsoft 365 email DNS in GoDaddy
Record the current public state for confirm active DNS is GoDaddy, restore MX, merge SPF safely. This gives the repair a before/after comparison and prevents a cached answer or a separate working service from being confused with the configuration that produced the symptom.
- Confirm active DNS is GoDaddy — Verify confirm active DNS is GoDaddy from the public Internet and compare it with the value the responsible provider says should be live.
- Restore MX — Read the public MX priorities and targets, then verify that each target itself resolves. A visible MX record is not enough if its mail hostname is broken.
- Merge SPF safely — Inspect the single public v=spf1 policy, validate its terms and count DNS-query-causing mechanisms; duplicate policies or excessive lookups can invalidate SPF.
- Validate autodiscover if required — Verify validate autodiscover if required from the public Internet and compare it with the value the responsible provider says should be live.
Repair steps in godaddy
Restore Exchange Online MX and SPF records in GoDaddy DNS, preserving any additional legitimate senders in the single SPF record.
- 1. Confirm active DNS is GoDaddy. After this step, check the public value tied to confirm active dns is godaddy before changing another unrelated setting.
- 2. Restore MX. After this step, check the public value tied to restore mx before changing another unrelated setting.
- 3. Merge SPF safely. After this step, check the public value tied to merge spf safely before changing another unrelated setting.
- 4. Validate autodiscover if required. After this step, check the public value tied to validate autodiscover if required before changing another unrelated setting.
Why this order matters for godaddy
The sequence begins with the provider/authority decision, then moves through confirm active DNS is GoDaddy, restore MX, merge SPF safely. That keeps the change scoped to the failed business-email DNS and mail authentication path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.
Verify Fix Microsoft 365 email DNS in GoDaddy
The public MX/authentication records should match the intended mail provider, required hostnames should resolve, and the relevant SPF/DKIM/DMARC check should no longer show the original failure. Compare the same confirm active DNS is GoDaddy and restore MX evidence used before the change; a repair is complete when the public result agrees, not merely when the godaddy interface reports that a save succeeded.
If godaddy and the public result disagree
Check whether the edited zone is authoritative, whether the exact root/www/subdomain was changed, whether a proxy state alters the visible endpoint, and whether a prior TTL can still exist in recursive caches. Do not add a second conflicting confirm active DNS is GoDaddy value to force validation.
Mistakes to avoid for this repair
Do not copy tenant-specific or region-specific values from another account, delete working email records during a website repair, change nameservers as a shortcut, or alter SSL/proxy modes without evidence from the origin. Fix Microsoft 365 email DNS in GoDaddy should change only the settings required by this diagnosis.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.