Skip to content

Commit 26c0c74

Browse files
[DNS] Update General DNS faq with hostname not covered (#19121)
* [DNS] Update faq.mdx * Apply suggestion from code review * Move monospaced warning quote from h2 to body --------- Co-authored-by: Rebecca Tamachiro <[email protected]> Co-authored-by: Rebecca Tamachiro <[email protected]>
1 parent c20707f commit 26c0c74

File tree

1 file changed

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

1 file changed

+10
-0
lines changed

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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -250,3 +250,13 @@ For example, if you need to resolve `example.com` through Cloudflare in your loc
250250
```txt
251251
example.com CNAME example.com.cdn.cloudflare.net
252252
```
253+
254+
---
255+
256+
## Why am I getting a warning for hostname not covered even if I have a custom certificate?
257+
258+
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.
259+
260+
`This hostname is not covered by a certificate.`
261+
262+
The warning will be gone when you upload a new custom certificate, or start using another type of certificate for this hostname.

0 commit comments

Comments
 (0)