'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Microsoft 365 Email Not Working After GoDaddy DNS Changes
Question details
The user's Microsoft 365 email stopped sending and receiving messages, and admin center access fails after modifying GoDaddy DNS records.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Updating custom domain DNS records in GoDaddy to point to Microsoft 365 services.
- Observed behavior
- Email routing stops working completely, and the Microsoft 365 admin account is reported as nonexistent during login attempts.
Ensure you have the login credentials for your original Microsoft 365 'onmicrosoft.com' administrator account, as your custom domain login may be temporarily unavailable due to DNS propagation.
Verify DNS Records and Use Fallback Admin Account
Use your default onmicrosoft.com account to regain access to the admin center and verify your MX and TXT records.
When custom domain DNS records are altered or propagating, Microsoft's authentication systems might momentarily fail to recognize the domain. Logging in with the default tenant domain bypasses this issue.
Go to the Microsoft 365 admin center and log in using the tenant's original administrator account (e.g., admin@yourtenant.onmicrosoft.com).
Open Outlook on the web (OWA) and attempt to send a test email. Note any Non-Delivery Report (NDR) or bounce-back messages received, as these contain specific routing errors.
Visit a DNS diagnostic service like MXToolbox. Enter your domain name to check if the MX, TXT (SPF), CNAME, and Autodiscover records are correctly pointing to Microsoft 365.
If your records appear correct in GoDaddy but the issue persists after 24 hours, contact Microsoft Support using the admin center help widget. Provide the exact sign-in errors and bounce-back messages.
Try WPS Office as Your Reliable Office Suite
While troubleshooting Microsoft 365 backend and DNS issues, you can continue your daily document work without interruption. WPS Office is a free, lightweight, and easy-to-use alternative that lets you create, edit, and manage your documents seamlessly.
- 1. Download and Install: Visit the WPS Office website and download the free installer for your operating system.
- 2. Open Your Files: Launch WPS Office and directly open your existing Word, Excel, or PowerPoint files to continue working.
- 3. Save Locally or Share: Save your progress locally in standard Office formats, ready to be emailed once your domain routing is restored.
Frequently Asked Questions
Why does Microsoft 365 say my email address doesn't exist after a GoDaddy DNS change?
If your custom domain's DNS records are incorrectly configured or haven't fully propagated, Microsoft's authentication servers may fail to associate your custom domain with your specific tenant. Using the default .onmicrosoft.com alias bypasses custom domain routing issues.
How long does it take for GoDaddy DNS changes to take effect for Microsoft 365?
Typically, DNS changes made in GoDaddy propagate within 1 to 4 hours. However, depending on the Time to Live (TTL) settings of your previous records, it can occasionally take up to 48 hours for all global servers to recognize the new Microsoft 365 routing.
Which DNS records are required for Microsoft 365 email to function properly?
To send and receive emails via Microsoft 365, your GoDaddy DNS must have an MX record pointing to Microsoft's mail servers (e.g., yourdomain-com.mail.protection.outlook.com), a TXT record for SPF to prevent spam filtering, and CNAME records for Autodiscover to connect Outlook client apps.
How can I check if my MX records are correct without logging into Microsoft 365?
You can use free third-party DNS diagnostic tools like MXToolbox. Simply enter your domain name in the MX Lookup tool, and it will query the public internet to display the current active mail servers routing traffic for your domain.
