הפץ אתר לחשבון ה-CDN שלך

You can serve a site from your own CDN account instead of ours — one you pay for, hold the credentials to, and can see in your own vendor dashboard. This is what "BYO CDN" means on your plan, and this article is how you actually use it.

What you need first

A CDN account of your own, connected to Zinn®. Go to Connections and add the account. You give us an API token scoped to that account; we store it in a vault and never show it again.

You can connect more than one. That is the point: an agency that keeps client work on one Cloudflare account and its own sites on another connects both, names them, and picks per site. Give each one a name you will recognise later — "CF — client work" is useful, "Cloudflare" twice is not.

Putting a site on it

Open the site, then the CDN tab. Under Where this site is served from you will see every destination this site can go to:

• Zinn® edge network — our pool. The default, included with your plan.
• One row per account you have connected, by the name you gave it.
• Your own edge (passthrough) — you run the CDN yourself and we just point the domain at it.

Choose one and confirm. We create the zone on that account, point your domain at it, and only then tidy up the one it came from.

What actually happens, and how long it takes

The order matters and it is the reason this is safe:

1. We build the zone on the account you chose and read it back.
2. We publish the new edge as your domain's answer.
3. We record the change on your site.
4. We wait.
5. Only once your domain really is answering from the new account do we remove the old zone.

Step 4 is the important one. Cloudflare gives every account its own pair of nameservers, so moving a site between two Cloudflare accounts changes the nameservers your domain must be delegated to. Until your registrar points at the new pair, visitors are still resolving through the old one.

If the domain is registered with us, we set the nameservers for you and the move usually finishes within the hour.

If it is registered somewhere else, we show you the new nameservers and wait. Copy them into your registrar's control panel. Nothing breaks while you take your time: both edges serve your site throughout, and we do not remove anything until the new one is answering.

Once your registrar is updated, propagation is typically minutes to a few hours, and can be up to 48 hours depending on the previous TTL. That is a property of DNS, not of us.

If something goes wrong

Every step can be undone and every failure leaves your site up. If the account refuses the zone, or the credential has been revoked since you connected it, nothing moves — your site carries on being served exactly where it was, and the tab tells you which step failed.

You can also cancel a move that is waiting for your registrar. Your site goes back to the account it was on, and the zone we built is removed.

A note if you are on Footprint-Free

Every site on one CDN account can be linked to every other site on it — that is exactly the connection the Footprint-Free line exists to prevent. Moving a Footprint-Free site onto a single account of your own is allowed, and we ask you to confirm you understand it first. Sites on our pool are spread across many accounts specifically so that they cannot be tied together.

What it does not change

Your plan, your slots and your bill with us stay the same. What changes is who is billed for the edge traffic: on your own account, that is you and your vendor. If we were unable to remove the old zone for any reason we say so on the tab, because you would otherwise keep paying two vendors for one site.