> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/groups/overleaf-group-single-sign-on/domain-management/troubleshooting-domain-management.md). # Troubleshooting domain management Setting up domain management involves aligning your organization's DNS, your SSO Identity Provider, and Overleaf’s automated verification systems. If something isn't working as expected, most issues can be resolved by checking public DNS records or verifying your SSO attributes. If you cannot identify the root cause or require direct assistance, please contact [Overleaf Support](https://www.overleaf.com/contact). ## When to contact Overleaf Support | **If you are experiencing...** | **Root Cause** | **Your Next Step** | | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Domain capture table and options are not found on the group admin's group settings | Your group is not currently participating in the limited beta for this feature. | Contact [Overleaf Support](https://www.overleaf.com/contact) to express your interest | | Domain capture is not enabled | Your SSO setup may not be complete, or the feature has not been enabled by Overleaf Support for your group. |

Verify your SSO setup, and
contact Overleaf Support to request that domain capture be enabled.

| | DNS `dig` or `nslookup` query returns no results or old data. | DNS records are still propagating across the internet. | Wait 24–48 hours for your registry to sync. | | Public DNS queries return the correct token, but Overleaf status is still "Failed". | Local network block or validation edge-case. | Contact [Overleaf Support](https://www.overleaf.com/contact) for an internal sync check. | | Domain status is "Verified" but capture status is "Inactive". | You may not have requested confirmation and activation of your domain capture, or activation may be delated. | Contact [Overleaf Support](https://www.overleaf.com/contact) (or reply to your verification email) to activate live capture. Note that the confirmation and activation process can take up to two business days. | ## Domain management troubleshooting FAQs
Overleaf is unable to verify the DNS TXT record, but it seems to be correctly configured on our side. How can I check on this? If our system cannot find your verification record, but your IT team confirms it has been added, you can manually query the public DNS to check on the record. Open your terminal (Mac/Linux) or Command Prompt (Windows) and run the appropriate command below on a public network.\ \ Replace `example.com` with your actual domain name. This should return the value of the Overleaf verification token (along with other TXT tokens that have been configured here.\ \ **For Mac / Linux (dig)** Run the following command to query public DNS resolvers (like Google) specifically for TXT records: ``` dig TXT example.com +short ``` **For Windows (nslookup)** Run the following command to query for TXT records: ``` nslookup -type=TXT example.com ``` Alternatively, you can use **Google Admin Toolbox Check DNS** tool, rather than the command line. 1. Go to the **Google Admin Toolbox Dig Tool**: 2. Enter your domain name (e.g., example.com) into the Name field. 3. Click the TXT button. If the TXT record is not found, or its value does not match the expected token, check your DNS Record configuration, or ask your IT Services team to check this. If the TXT record is found and matches your token, please contact Overleaf support.
My domain seems stuck in the pending or failed state. What should I do? This may be because the DNS record has not been configured as expected, that it is not accessible publicly, or may be caused by some other technical issue that our support team can help troubleshoot. Please follow the instructions above on manually checking that the DNS record is publicly accessible. The next step would be to [reach out to Overleaf Support](https://www.overleaf.com/contact) and request that we check on the status of the verification directly.
My domain has been verified but is still inactive. What are the next steps? Once verified, domain capture will remain inactive while the Overleaf support team confirms that claimed domains are exclusively associated with your subscription on the Overleaf side. Overleaf Support will not confirm and activate your domain unless requested. To start the confirmation and activation process, please reply to the successful verification email that is sent to the subscription administrator, or [send a request to Overleaf Support](https://www.overleaf.com/contact). This process can take up to two business days.
Why do I not see the domain management option in my Subscription settings? If you are the administrator of a Group Pro subscription with Managed Users enabled, you should find the domain management section in your Group settings. This option may not be immediately visible on all subscriptions, depending on when that subscription was purchased and initially configured. If you do not see this section, please [contact Overleaf support](https://www.overleaf.com/contact) with a request to have domain management enabled on your subscription.
Why are some users with our domain not being automatically enrolled? If domain capture is active but certain team members are still creating independent, unmanaged accounts, it may be that they are registering in Overleaf under a subdomain of one of your verified and captured domains. Please check the exact structure of the email addresses of users who are not being captured. If your root domain (`example.com`) is verified, but users are signing up with a subdomain email (like `name@engr.example.com`), they will not be captured. **The Fix**: Add the specific subdomain to your domain management table and follow the standard verification and capture activation process for it.
Users are seeing errors when signing in with SSO. What is the cause of the problem? Please see the section on user errors in the [Maintaining Group SSO documentation](https://docs.overleaf.com/groups/overleaf-group-single-sign-on/maintaining-group-sso) for an overview of some login errors and their causes.
--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.overleaf.com/groups/overleaf-group-single-sign-on/domain-management/troubleshooting-domain-management.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.