Nine providers
Cloudflare, deSEC, Hetzner DNS, ClouDNS, Bunny DNS, Azure DNS, Amazon Route 53, DigitalOcean DNS and Gcore.
Your own DNS
Serve DNS from your own account
Keep your zones where they are. Connect your own Cloudflare, deSEC, Hetzner DNS, ClouDNS, Bunny DNS, Azure DNS, Amazon Route 53, DigitalOcean DNS or Gcore account, and the records your sites need are written to it. We test the key before we save it.
What it is
A connection to the DNS account where your zones already live. Paste a key into Integrations and we test that it can read your zones, read their records and edit a record before anything is saved.
Your zones and your provider contract stay exactly where they are. The dashboard works on the account you connected, rather than asking you to move a domain's DNS to us.
What you get
Nine providers, all tested the same way.
Three permissions, tested
Zone read, record read and record edit are each checked before the key is saved, and you see which passed.
Your zones stay put
Connecting does not move your zones. They stay on your own account with your provider.
Stored encrypted
A key that passes is kept encrypted in our secrets vault, never in a database column or a log line.
Disconnect deletes the key
Disconnecting removes the stored key. Your zones and records remain with your provider.
Step-by-step guides
Each guide shows where to create the key on the provider's side, what it needs, and how to connect it in the dashboard.
Bring your own accounts: the overview
Read the guide →Cloudflare
Read the guide →deSEC
Read the guide →Hetzner DNS
Read the guide →ClouDNS
Read the guide →Bunny DNS
Read the guide →Azure DNS
Read the guide →Amazon Route 53
Read the guide →DigitalOcean DNS
Read the guide →Gcore
Read the guide →How it works
Three steps, and your zones never leave your account.
Create a key with your provider
Create an API token in your DNS account with access to the zones you want to use. Each provider's guide shows how.
Connect it in Integrations
Paste it in. Zone read, record read and record edit are tested before it is saved.
Use it for your sites
Once connected, the records your sites need are written to your own zones on that account.
Pricing
Using your own DNS account is not an add-on.
We charge nothing for the connection. Your DNS provider bills you directly, on your own account, if it charges at all. Your Zinn Digital® hosting plan is billed as normal.
Query, zone and feature prices are your provider's, on your account. We never add to them.
Why it is built this way
DNS is what every visit to a domain depends on, and plenty of teams have good reasons to keep it with a provider they chose. Driving that account from the dashboard means you do not have to move it to host with us.
Record edit is tested before saving because DNS failures are quiet: a key that can read but not write looks fine until the first change silently does not happen.
Questions people ask before they buy
Which DNS providers can I connect?
Cloudflare, deSEC, Hetzner DNS, ClouDNS, Bunny DNS, Azure DNS, Amazon Route 53, DigitalOcean DNS and Gcore, each on your own account.
What permissions does the key need?
Zone read, record read and record edit. We test all three before saving and show you the result.
Do my zones move to you?
No. The key works on the zones already in your account, and they stay with your provider.
Who bills me for DNS?
Your DNS provider, directly, if it charges. The connection costs nothing from us, and your hosting plan is billed as normal.
How is my key stored?
Only after it passes the tests, and then encrypted in our secrets vault. Disconnecting deletes it.
Help with this
Step-by-step guides from our knowledge base, written for exactly this.
Send email from your own domain, on your own account
Send your clients' notifications from your own domain, on your own mail account: which provider to choose, the SPF, DKIM and return-path records they all need, why we insist a test message actually arrives, and what happens when a provider breaks.
Read the guide →Giving clients their own CDN and DNS
Pools, bring-your-own accounts, and why footprint separation needs more than one account.
Read the guide →Connecting a domain you already own
Keep it where it is registered and point it here — the two ways, and which to choose.
Read the guide →Connect your DNS account
Create an account, open Integrations and paste in a token from your DNS provider. Zone read, record read and record edit are tested before it is saved.
Get started