> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/organization-and-account-settings/domains/retry-failed-custom-domain.md).
# Retry failed custom domain
{% hint style="success" %}
**Access Type:** Domains - Editor
{% endhint %}
When your organization submits a custom domain, Didomi will verify that the correct NS records are correctly configured before provisioning in Amazon Web Services (AWS). In instances where verification fails Didomi will change the [domain status](/organization-and-account-settings/domains/domain-status-glossary.md) to **Failed**. Some reasons for a custom domain failing verification include:
* DNS records not propagated yet
* Didomi processing error
In this article, we will cover how to resubmit a custom domain after it has failed verification.
{% hint style="info" %}
Ensure that the DNS have fully propagated before resubmitting the custom domain. Your organization can utilize a tool such as [DNS Checker](https://dnschecker.org/#NS) to check for propagation.
{% endhint %}
Click **My organization** and select **Organization settings** from the drop-down menu.
Ensure the **Domains** tab is selected and navigate to a custom domain on the subsequent list with a **Failed** status.
Click the **relaunch** icon inline with the custom domain.
Confirm that your DNS records are created and fully propagated in the subsequent modal and click **Yes** to continue.
Didomi will attempt to verify and create your custom domain again.
---
# 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.didomi.io/organization-and-account-settings/domains/retry-failed-custom-domain.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.
