“Via the CDN” with one switch
One switch per name: it points to the edges instead of directly to your server – even for the bare domain. New websites and game servers are switched over automatically.

Move your DNS zones in a few steps – without downtime. Then websites and game servers go through the CDN with one switch, with DNSSEC, DynDNS and a history that can undo every change.
Your domain stays with your registrar – only the name servers change. The zone is already being served before you switch.
Enter your domain – the CDN looks up the usual records (www, mail, MX, SPF, DKIM …) and imports them.
With the zone file from your previous provider or an API token from Cloudflare or Hetzner. The wizard checks website, MX, SPF and DMARC.
At your registrar, to the CDN’s two name servers. The portal checks live and reports “Done”.
ns1.cdn.kernhosting.com ns2.cdn.kernhosting.com # Delete the old zone a few days later – # until then, both answer correctly.
One switch per name: it points to the edges instead of directly to your server – even for the bare domain. New websites and game servers are switched over automatically.
A, AAAA, CNAME, MX, TXT, SRV, CAA and NS – with templates for Microsoft 365, Google Workspace, DMARC and Let’s Encrypt (CAA).
Every change with author and before/after state. One click reverts it – even whole imports. Export as CSV.
Signed answers protect against forged DNS responses. Switch it on, add the DS record at your registrar – the CDN checks and reports “active”.
For servers with a changing address: your router, dyndns2 routers, ddclient or a script report the new address. If the name goes via the CDN, your home address stays hidden.
*.your-domain.com through one website – and DNS validation via API for lego or certbot, e.g. for your mail server.
ns1 and ns2 are located in different networks. Names via the CDN have a TTL of at most 5 minutes – if an edge fails, visitors quickly reach the next one.
The portal warns while you type: a public resolver as address, private IPs, fixed edge addresses or duplicate SPF records.
MX, SPF and DKIM stay as they are. The migration wizard checks them before you switch.
Import records with a Cloudflare token, add names behind the orange cloud as websites, switch name servers – without downtime. All data stays in Germany, with no US service in between.
| Cloudflare | KernHosting CDN |
|---|---|
| Orange cloud (proxy) | “Via the CDN” on the DNS record, or a website in the CDN |
| Page Rules, Redirect Rules | Redirects and header rules |
| Cache Rules | Cache rules |
| WAF, Firewall Rules | WAF |
| IP Access Rules, countries | IP and country blocking |
| Rate Limiting | Rate limits per path |
| “I’m Under Attack” | “Under attack” mode |
| Bot Fight Mode | Bots |
| SSL/TLS “Full (strict)” | HTTPS connection with server certificate check |
| Authenticated Origin Pulls | Origin protection |
We don’t offer Workers, Pages, R2 or Zero Trust. See the full comparison on the overview.
No. You can also set individual DNS records with your provider. With the zone at the CDN, however, the bare domain goes via the CDN too – without fixed addresses or ALIAS.
Yes, you keep paying for it there. Only the name servers change.
Yes, as long as MX, SPF and DKIM are imported. The wizard checks MX, SPF and DMARC before you switch; there are templates for Microsoft 365 and Google Workspace. Mail names like mail or imap deliberately don’t go via the CDN.
If DNSSEC is active at your registrar, switch it off before moving and wait a day. The wizard warns you if a DS record is still in place. After the move, switch DNSSEC on at the CDN.
Not yet – zone transfers and custom name server names aren’t possible at the moment.

Free plan, forever · no credit card required · set up in minutes
Privacy
No cookies. No tracking.
We only store your choice between the light and dark design and that you closed this notice – locally in your browser.