JSOPanel Get started
Help Center › Administrators › Connecting a domain to Cloudflare

Connecting a domain to Cloudflare

How to link a domain's DNS management to a Cloudflare account.

Some customers prefer to manage a domain's DNS through Cloudflare, for its content delivery network, additional protection, or simply because they're already using it. JSOPanel can connect a domain's zone to Cloudflare so that records you add or edit here are sent there too.

Before you start

You'll need a Cloudflare API token with permission to edit DNS for the zone in question. Create it from your Cloudflare account under My Profile, API Tokens.

Connecting one domain

  1. Click DNS Zones in the sidebar and choose the domain.
  2. Open the Cloudflare tab.
  3. Paste in your Cloudflare API token and click Connect. It's checked against Cloudflare before it's saved.

Once connected, you can press Make Cloudflare match this server to push every record in this domain's zone there. Read the confirmation carefully first: this also deletes anything at Cloudflare that isn't in this domain's zone here, so a verification record you only ever added directly in Cloudflare would be removed. You can also put the domain behind Cloudflare's proxy (the orange cloud) from the same tab.

Connecting a whole Cloudflare account at once

If you manage many domains in one Cloudflare account, you can instead save that account's own API token once, on any domain's Cloudflare tab, then press Connect ALL my domains at once. You're asked to confirm first, every domain whose zone is in the saved Cloudflare account gets connected; domains already connected, or whose zone isn't in that account, are left alone.

Subdomains of a connected domain

If a subdomain belongs to a parent domain that's already connected to Cloudflare, its records live inside the parent's own Cloudflare zone rather than getting a separate one. The subdomain's own DNS Zones page links straight to the parent's Cloudflare tab for editing those records.

Disconnecting

Press Disconnect on the domain's Cloudflare tab at any time. This deletes the saved token here and JSOPanel stops sending changes to Cloudflare for that domain; it doesn't remove any records already there, and DNS is only actually served by JSOPanel again once the domain's nameservers are pointed back.

Tip: if a domain's nameservers still point at Cloudflare after disconnecting, DNS continues to be controlled from Cloudflare's own dashboard, regardless of what JSOPanel shows.