'%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 SharePoint Site Inaccessible with DNS_PROBE_FINISHED_NXDOMAIN Error
Question details
Users are unable to access a previously functioning SharePoint site, encountering a DNS probe finished NXDOMAIN error in their web browser.
- Product
- SharePoint
- Device & OS
- not provided
- Scenario
- Attempting to access a SharePoint URL through a standard web browser.
- Observed behavior
- The browser fails to load the page and displays a DNS_PROBE_FINISHED_NXDOMAIN error message, indicating the site is unreachable.
Verify that your internet connection is active by visiting other standard websites to ensure it is not a complete network outage.
Test with an Alternative Network and Browser
Switching your network and browser helps isolate whether the DNS error is a local system issue or a wider service problem.
Local network caching or specific browser configurations can sometimes cause domain name resolution failures. Ruling these out is the best first step before escalating the issue.
Disconnect from your current Wi-Fi or wired network and connect to an entirely different network, such as a mobile data hotspot.
Open a different web browser (for example, if you are using Chrome, try Edge or Firefox) and attempt to load the SharePoint site again.
If the site loads on a different browser, clear the cache and cookies in your original browser from the settings menu.
Submit a Service Request in the Microsoft 365 Admin Center
If the site remains inaccessible across multiple networks and browsers, the issue likely resides with the Microsoft 365 tenant or SharePoint backend servers.
Need a Reliable Offline Office Suite? Try WPS Office
While resolving complex SharePoint backend or DNS issues, you might need a stable offline tool to view and edit your documents. WPS Office provides a free, lightweight, and fully compatible alternative to Microsoft Office, ensuring your productivity isn't halted by network or cloud errors.
- 1. Download the software: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install and launch: Follow the on-screen instructions to install the application, then launch WPS Office.
- 3. Open and edit files: Open your local documents directly. Any edits you make can be saved in standard Microsoft formats, ready to be uploaded to SharePoint once the service is restored.
Frequently Asked Questions
What does the DNS_PROBE_FINISHED_NXDOMAIN error mean?
This error means that the Domain Name System (DNS) could not resolve the web address into an IP address. 'NXDOMAIN' stands for Non-Existent Domain, indicating the browser cannot find the server hosting the SharePoint site.
Why is only my SharePoint site affected while other sites load normally?
This usually indicates an issue specific to your Microsoft 365 tenant's routing, a temporary outage on Microsoft's SharePoint backend, or a highly specific local DNS caching error for that exact URL.
Do I need admin rights to fix this issue?
If the issue is local, you can troubleshoot it by switching networks or clearing your browser cache without admin rights. However, if a Microsoft 365 backend issue causes it, you will need a tenant administrator to open a support ticket with Microsoft.
