You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/dns/troubleshooting/faq.mdx
-11Lines changed: 0 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -227,17 +227,6 @@ This is important because, if a domain is in a _Moved_ state for a [long enough
227
227
228
228
---
229
229
230
-
## How to configure records on local DNS servers?
231
-
232
-
You can create CNAME records pointing to `cdn.cloudflare.net` in your local DNS to locally resolve hostnames through Cloudflare.
233
-
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:
234
-
235
-
```txt
236
-
example.com CNAME example.com.cdn.cloudflare.net
237
-
```
238
-
239
-
---
240
-
241
230
## Why am I getting a warning for hostname not covered even if I have a custom certificate?
242
231
243
232
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.
0 commit comments