Skip to content

[DNS] Update faq.mdx #25038

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 12, 2025
Merged

[DNS] Update faq.mdx #25038

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 0 additions & 11 deletions src/content/docs/dns/troubleshooting/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -227,17 +227,6 @@ This is important because, if a domain is in a _Moved_ state for a [long enough

---

## How to configure records on local DNS servers?

You can create CNAME records pointing to `cdn.cloudflare.net` in your local DNS to locally resolve hostnames through Cloudflare.
For example, if you need to resolve `example.com` through Cloudflare in your local DNS server, you need to create a CNAME record such as:

```txt
example.com CNAME example.com.cdn.cloudflare.net
```

---

## Why am I getting a warning for hostname not covered even if I have a custom certificate?

If the [custom certificate](/ssl/edge-certificates/custom-certificates/) has been in place before our new certificate management pipeline, the following warning is displayed but can be discarded.
Expand Down
Loading