Skip to content

[DNS] Update faq.mdx #19121

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 3 commits into from
Jan 15, 2025
Merged

[DNS] Update faq.mdx #19121

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d605999
[DNS] Update faq.mdx
ngayerie Jan 10, 2025
e4075da
Apply suggestion from code review
RebeccaTamachiro Jan 15, 2025
cc759f9
Move monospaced warning quote from h2 to body
RebeccaTamachiro Jan 15, 2025
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
7 changes: 7 additions & 0 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 @@ -250,3 +250,10 @@ For example, if you need to resolve `example.com` through Cloudflare in your loc
```txt
example.com CNAME example.com.cdn.cloudflare.net
```

---

## Why am I seeing the warning `This hostname is not covered by a certificate` 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, this warning is displayed but can be discarded.
The warning will be gone when you upload a new custom certificate, or start using another type of certificate for this hostname.
Loading