> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/knowledge-base/troubleshooting-articles/domain-validation-troubleshooting.md). # Domain validation troubleshooting Troubleshoot Devolutions Cloud domain validation failures during SSO setup by checking your domain, DNS TXT record, and verification challenge. When [configuring single sign-on (SSO)](/cloud/getting-started/get-started-with-sso-in-devolutions-cloud.md) in your Devolutions Cloud, the first step is to ***Verify your domain***. If you encounter issues while attempting to validate your domain, check the following elements. ### Verify your domain Make sure that the domain you are entering is the one currently in use for your Devolutions Account and SSO tenants. It is crucial that the domain you are attempting to validate matches the one associated with your account. {% hint style="info" %} Tip: If your domain ends in `.loc`, it is likely not the correct one for this purpose. {% endhint %} ### Verify your DNS provider TXT Record Ensure that you have entered the "\_devolutions-challenge" subdomain as a TXT Record in your DNS provider. To confirm that it is correctly configured, you can use a DNS querying tool such as [MXToolBox](https://mxtoolbox.com/txtlookup.aspx) and input the domain as "\_devolutions-challenge.windjammer.co", for example. ### Verify your challenge Ensure that the challenge used in the domain contains the right string and starts with "DEVOLUTIONS-DOMAIN-VERIFICATION=". ### Retry domain verification 48 hours after the initial setup, the lookup stops if it is still not validated. You can then retry the domain validation process in Devolutions Cloud. To do so, go to ***Administration – Authentication – Domain*** and click ***Retry domain validation***. ### Contact our customer support team If you have went through the entire list and your domain verification is still unsuccessful, the issue may be deeper and require further investigation. In this case, it is recommended to contact our technical customer support team for assistance at . When reaching out to support, provide them with all the relevant information. This would include information such as: * The DNS provider you are using for your domain. * The physical region where your system is located. * The region where your Devolutions Cloud instance is located (found next to the version at the bottom of the navigation pane). Collecting this data will greatly assist our customer support team in diagnosing and addressing any underlying issues effectively. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.devolutions.net/cloud/knowledge-base/troubleshooting-articles/domain-validation-troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.