Skip to content

Commit bf3f6cf

Browse files
Remove no A, AAAA, or CNAME record found
1 parent 6468d96 commit bf3f6cf

File tree

1 file changed

+0
-14
lines changed
  • src/content/docs/dns/troubleshooting

1 file changed

+0
-14
lines changed

src/content/docs/dns/troubleshooting/faq.mdx

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -212,20 +212,6 @@ Third-party tools can sometimes fail to return correct DNS results if a recursiv
212212

213213
---
214214

215-
## No A, AAAA or CNAME record found?
216-
217-
`No A, AAAA or CNAME record found` means the Cloudflare **DNS** app lacks proper records for DNS resolution.
218-
219-
[Add the missing DNS records](/dns/manage-dns-records/how-to/create-dns-records) to your domain.
220-
221-
:::note
222-
223-
Sites generally have at least an `A` record that points to the origin
224-
server IP address, typically for the `www` subdomain and the apex domain (also known as "root domain" and represented by `@`).
225-
:::
226-
227-
---
228-
229215
## Why have I received an email: Your Name Servers have Changed?
230216

231217
For domains where Cloudflare hosts the DNS, Cloudflare continuously checks whether the domain uses Cloudflare’s nameservers for DNS resolution. If Cloudflare's nameservers are not used, the [domain status](/dns/zone-setups/reference/domain-status/) is updated from *Active* to *Moved* in the Cloudflare **Overview** app and an email is sent to the customer.

0 commit comments

Comments
 (0)