> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/troubleshooting/domain-verification/troubleshooting-verify-domain-dns.md).

# Troubleshoot domain verification with DNS

For Snyk API & Web to run full scans on your target, you must verify its domain. Visit [Verify domain ownership](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership.md) to learn why domain verification is required.

## The problem

Domain verification using CNAME or TXT records in your DNS fails with the following errors:

* DNS (CNAME) error: `The DNS query name does not exist: <your CNAME record>`
* DNS (TXT) error: `Token not found`

## Troubleshoot the problem

Work through the following steps to identify the possible causes and solutions.

### Check the TTL value

Check the Time to Live (TTL) as follows:

1. Navigate to [Google Admin Toolbox Dig](https://toolbox.googleapps.com/apps/dig/) and type the target's URL.
2. Depending on your domain verification method, click **CNAME** or **TXT** to see the TTL value.

If the TTL value is high, the DNS configuration with the CNAME or TXT record has not been propagated yet, and the domain verification fails.

| Cause                                                                           | Solution                                                                                                                                      |
| ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| The DNS configuration with the CNAME or TXT record has not been propagated yet. | Wait for the DNS configuration to propagate, or navigate to your authoritative DNS server (for example, Cloudflare) and reduce the TTL value. |

After following these steps and applying the solutions, you can verify your domain using DNS.

## Related articles

* [Verify domain ownership](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership.md)
* [Verify domain with DNS CNAME record](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership/verify-with-dns-cname.md)
* [Verify domain with DNS TXT record](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership/verify-with-dns-txt.md)


---

# 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.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/troubleshooting/domain-verification/troubleshooting-verify-domain-dns.md?ask=<question>&goal=<endgoal>
```

`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.