Nameservers
The no-code install: change two nameservers, and DNA runs your DNS and sits in front of your site.
Point your domain's nameservers at DNA and every request to your site passes through DNA on its way to your existing host. There is no package to install, no deploy, and no API key for traffic. Your site stays where it is.
DNA also runs the domain's DNS. You manage every record, mail included, in the dashboard or through the API.
How it works
- You connect the domain. DNA scans its DNS records and copies them into a new zone.
- You change two nameservers at your registrar.
- Once the change reaches the internet, DNA answers for the domain and forwards allowed requests to your site.
Set up
Connect a domain
Add the domain, review its records, and change the nameservers at your registrar.
Manage DNS records
Add and edit records in the dashboard, or import a zone file.
Shopify stores
Connect a store, and what DNA covers on it.
Disconnect a domain
Pause DNA, or move the domain's DNS somewhere else.
Nameservers or middleware
| Nameservers | Middleware | |
|---|---|---|
| You change | two nameservers | code or config you deploy |
| You run | nothing | middleware, worker, Snippet, or proxy |
| API key | none for traffic; a script that changes records needs one (API) | one per environment |
| DNS provider | DNA | yours, unchanged |
| Enforced traffic | requests that reach DNA | requests that reach your installed code |
| First request after | nameserver propagation | a deploy |
Classification, the labels, observe-first
defaults, and 403 on block work the same in both.