From d605999c74b978bec948405866388866aa03429b Mon Sep 17 00:00:00 2001
From: Nic <123965403+ngayerie@users.noreply.github.com>
Date: Fri, 10 Jan 2025 13:25:33 +0100
Subject: [PATCH] [DNS] Update faq.mdx

---
 src/content/docs/dns/troubleshooting/faq.mdx | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/src/content/docs/dns/troubleshooting/faq.mdx b/src/content/docs/dns/troubleshooting/faq.mdx
index 9b32e7142417c1..4ded571b96affd 100644
--- a/src/content/docs/dns/troubleshooting/faq.mdx
+++ b/src/content/docs/dns/troubleshooting/faq.mdx
@@ -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.