'%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)
How to Fix Recipient Domain Not Found Error in Microsoft 365
Question details
Senders are receiving bounce-back messages stating that the recipient domain is not found when attempting to send emails.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Sending emails to or from a Microsoft 365 domain that may have incomplete configuration.
- Observed behavior
- An error message is triggered indicating the recipient domain could not be found, typically caused by unverified domains or incorrect DNS records.
Ensure you have Global Administrator or Exchange Administrator privileges in your Microsoft 365 tenant, as well as access to your domain registrar's DNS settings.
Verify Domain Status and Check DNS Health
Use the Microsoft 365 Admin Center to ensure the domain is fully verified and run a health check to identify any missing or incorrect DNS records.
The most common cause for this error is a domain that was added to the tenant but not fully verified, or a domain whose MX and TXT records were recently changed or configured incorrectly.
Sign in to the Microsoft 365 Admin Center using your global administrator credentials.
In the left-hand navigation menu, click on Settings and then select Domains.
Locate the affected domain in the list. Ensure that it was added completely through the Add Domain wizard and check for any 'Incomplete setup' or 'Action required' notifications.
Click on the specific domain name, and then click the Check health button to run a diagnostic on your current DNS configuration.
If the health check reveals errors, follow the on-screen instructions to update the missing or incorrect MX, TXT, or CNAME records at your domain registrar.
Contact Microsoft 365 Technical Support
If your domain is verified and the DNS health check shows no errors, backend routing issues might require Microsoft Support intervention.
Discover WPS Office: A Powerful and Free Alternative to Microsoft 365
While resolving Microsoft 365 admin and domain issues can be time-consuming, managing your daily documents shouldn't be. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office. Enjoy seamless document editing, spreadsheet management, and presentation creation without the need for complex tenant configurations.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install the Suite: Run the downloaded installer file and follow the quick, one-click setup process.
- 3. Start Creating: Launch WPS Office and instantly open your existing Microsoft Office files to continue your work without missing a beat.
Frequently Asked Questions
Why am I getting a 'recipient domain not found' error if the email address is spelled perfectly?
Even with perfect spelling, this error occurs when the sending email server cannot locate the destination domain's MX (Mail Exchanger) records in the global DNS registry, or if the domain hasn't been properly verified within the recipient's Microsoft 365 tenant.
How long does it take for a newly added domain to verify in Microsoft 365?
Domain verification typically takes just a few minutes after you add the correct TXT or MX record to your DNS host. However, in some cases, it can take up to 48 hours for these DNS changes to propagate globally.
Can a standard user fix a domain not found error in Microsoft 365?
No, standard users cannot fix this issue because modifying domain settings requires administrative access. You must contact your organization's Global Administrator or IT support team so they can update the domain's DNS settings in the admin center.
