> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://docs.flyinghost.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Use your own Cloudflare account with FlyingHost (O2O)

You can host your site on FlyingHost and manage **security rules, redirects, and analytics** in your own Cloudflare account. This setup is called **Orange-to-Orange (O2O)**. Your Cloudflare rules apply before traffic reaches FlyingHost. [How O2O works](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/)

## Connect your domain

Your domain must use **Cloudflare DNS** in your own account.

![Domains tab in Cockpit showing where to start connecting a domain](https://storage.crisp.chat/users/helpdesk/website/-/3/5/a/3/35a3c3ffe31dc000/domains-tab_15u4qix.png)

- **Connecting a domain for the first time?** In FlyingHost, open your site and select **Domains → Connect domain**. For sites created after **November 11, 2026**, FlyingHost automatically provides the CNAME records below for domains using Cloudflare DNS. Check that the website records are **Proxied**.
- **Already connected?** Open **Cloudflare → DNS → Records**. If your website uses A records pointing to `104.17.15.101`, replace them with the CNAME records below. Your site can stay connected to FlyingHost while you update DNS.

| Type | Name | Target | Proxy status |
| --- | --- | --- | --- |
| CNAME | `@` | `"connect.flyinghost.app"` | Proxied 🟠 |
| CNAME | `www` | `"connect.flyinghost.app"` | Proxied 🟠 |

Enter the CNAME target shown in the table without the quotation marks.

### Check DNS and HTTPS

For a site on a subdomain such as `blog.example.test`, use `blog` as the record name instead. O2O requires the website CNAME to be proxied.

Keep the `_acme-challenge` certificate validation record set to **DNS only** (gray cloud).

After saving, open your site over HTTPS. If you use both the root domain and `www`, check both.

## What you can manage in Cloudflare

- WAF rules and rate limiting
- Redirects
- Page Rules and Transform Rules
- Cloudflare Access
- Workers
- HTTP traffic and security analytics

FlyingHost already manages caching. Avoid adding a **Cache Everything** rule in your account, since a second HTML cache can serve outdated pages.