Giving clients their own CDN and DNS

By default your clients' sites use our CDN and DNS accounts. For most resellers that is right. Two situations change it.

When a client should have their own

They already have an account and want to keep it — their team knows it, their rules live in it, and moving is disruption for no gain. Reseller → Networks → add their account, and their sites use it from then on.

Footprint separation. Sites that must not look related should not share a nameserver, an IP or a CDN account, because those are exactly the joins somebody looks for. A pool of accounts, with sites distributed across them, is what breaks the join.

Pools

A pool is a set of accounts we spread sites across. You add accounts — yours, ours or a client's — and choose how sites are allocated: round-robin, or grouped so a client's own sites stay together while different clients never share.

Reseller → Networks → Pools shows how many sites each account carries and warns before an account reaches its own provider's limit.

Nameservers

Whichever account a zone lands in, your clients see your nameservers if you have set them up — ns1.yourbrand.com rather than anything of ours. That is the single most visible part of white-labelling and it is worth doing.

⛔ Check the client's account limits before you rely on it. A free-tier CDN account has a zone cap, and the failure arrives as "the site will not go live" on the day you least want it.