[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]>
cloudflare · Jan 15, 2025 · 26c0c74 · 26c0c74
1 parent c20707f
commit 26c0c74
Showing 1 changed file with 10 additions and 0 deletions.
diff --git a/src/content/docs/dns/troubleshooting/faq.mdx b/src/content/docs/dns/troubleshooting/faq.mdx
@@ -250,3 +250,13 @@ 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 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.
+
+`This hostname is not covered by a certificate.`
+
+The warning will be gone when you upload a new custom certificate, or start using another type of certificate for this hostname.