Cloudflare
Ours or yours. The multi-account footprint pool behind the Footprint-Free line, and a first-class Mainstream CDN — full SSL enforced, never flexible.
CDN & DNS providers
Your CDN and DNS, chosen per site
CDN and DNS are a per-site choice, selected at deploy and controllable from the dashboard and the MCP. The Footprint-Free line rotates across a pool for footprint diversity; the Mainstream line picks per site. Every provider supports both the apex and www — you pick the canonical, the other redirects — and you can always bring your own account.
- CDN + DNSchosen per site at deploy
- Apex + wwwon every provider
- PBN rotatesfor footprint diversity
- Bring your ownon top of ours
CDN providers
The content-delivery networks the platform drives, plus anything you bring. On the Footprint-Free line these rotate across a pool; on the Mainstream line you select per site.
BunnyCDN
Ours or yours. A cheap, fast footprint-pool provider with no apex or www limitations.
CDN77
Bring your own. A capable edge; the apex-and-www rule is handled for you. We do not run CDN77 accounts ourselves, so this one is yours to hold.
KeyCDN
Bring your own. Connect your KeyCDN account and we drive it — zones, aliases, HTTPS and purge — with apex and www handled our end.
Fastly
Bring your own. A more advanced edge with instant purge; connect your Fastly account and we drive the service, its domain and its TLS.
Gcore
Bring your own. A fast global edge; connect your Gcore account and we drive its CDN resources and purge.
Amazon CloudFront
Bring your own. The commonest account customers already have. Note CloudFront needs your own certificate in the us-east-1 region before it will serve your domain — we tell you if it is missing.
Akamai
Bring your own. You keep your property configuration in Akamai; we detect the hostname, show which edge it maps to, and purge it from here.
Bring your own CDN
Connect an account you already run — full integration for popular providers, or DNS-delegation passthrough for anything else.
DNS providers
The nameserver providers in the pool. Diversity here is a footprint feature in its own right, so the set favours cheap, anycast providers you can spread a network across.
Cloudflare
Live. Free at any scale with strong anycast. On Cloudflare CDN, DNS is always Cloudflare — the zone and the CDN are one.
Zinn® nameservers (ours)
Live. Zinn-branded nameservers for the Mainstream line. A branded nameserver is itself a footprint, so it is not used on the PBN line.
ClouDNS
Live. Cheap, anycast and predictably priced — good pool diversity.
Azure DNS
Live. Full apex and arbitrary-subdomain support; the old www-only behaviour was a footprint flag, not a provider limit.
Bunny DNS
Live. Cheap anycast that pairs with the BunnyCDN account, for near-zero-cost nameserver diversity.
deSEC
Live. Free, non-profit anycast with DNSSEC and an API — near-zero-cost diversity for the pool. Bring your own DNS is supported too.
Hetzner DNS
Live. Free DNS hosting with a straightforward API from an established European host — more anycast diversity at no per-zone cost.
Amazon Route 53
Bring your own. The DNS most AWS customers already run; connect the account and we drive the zone and its records from here.
DigitalOcean DNS
Bring your own. Free DNS on an account many teams already have; connect it and we drive the zone and its records from here.
The rules that make any combination work
A few locked rules keep provider choice flexible without ever producing a broken or duplicate-content setup.
- Every CDN and DNS provider supports both the apex (non-www) and www — you choose the canonical at deploy and the other 301-redirects to it.
- On Cloudflare CDN, DNS is always Cloudflare; on every other CDN you pick the DNS provider freely from the pool.
- On the Footprint-Free line the platform rotates providers across a pool for footprint diversity; on the Mainstream line you choose per site.
- CDN and DNS are a deploy-time, per-site choice on the dashboard and the MCP, so bulk and AI-driven selection is first-class.
- You can bring your own CDN or DNS account and use it alongside ours, across both product lines.
FAQ
Which CDN providers can I use?
You can bring your own account on Cloudflare, BunnyCDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront or Akamai, and we drive it for you. On the accounts we run ourselves — Cloudflare and BunnyCDN — the Footprint-Free line rotates across a pool for footprint diversity, and on the Mainstream line you pick the provider per site.
Which DNS providers can I use?
Cloudflare, ClouDNS, Azure DNS, Bunny DNS, deSEC and Hetzner DNS are all live, plus bring-your-own on Amazon Route 53 and DigitalOcean DNS. Our own branded nameservers, ns1 and ns2 at zinndigital.com, answer on global anycast and are a Mainstream-line option — a branded nameserver is itself a footprint, so it is not used on the PBN line.
Does every provider support a bare domain, not just www?
Yes. Every CDN and DNS combination supports both the apex (example.com) and www.example.com. You choose the canonical at deploy and the other 301-redirects to it, so there is no duplicate-content split and no www-only limitation.
Can I mix any CDN with any DNS?
Almost. On every CDN except Cloudflare you pick the DNS provider freely from the pool. The one fixed rule is Cloudflare: on Cloudflare CDN, DNS is always Cloudflare, because the zone and the CDN are the same thing there.
Why so many DNS providers?
For the Footprint-Free line, nameserver diversity matters as much as cost — every site sharing one nameserver set is a footprint. Running a spread of cheap, anycast providers gives that diversity without a per-zone bill, which is why the pool favours flat and free-priced providers.
Related
Choose your providers
Start a card-free 14-day trial and pick your CDN and DNS per site — or let the Footprint-Free pool rotate for you — with apex and www on every provider, from the dashboard and the MCP.
Start free