One dashboard for every client domain
Stop logging into 20 different registrars and DNS panels. Manage every client’s DNS from one NexDNS account with scoped API keys, bulk operations, and an API that fits your automation.
The DNS bottleneck in agency work
When your clients' DNS lives at 20 different providers, simple changes become multi-hour tasks.
Scattered DNS across registrars
Each client’s DNS is wherever the domain was registered – GoDaddy, Namecheap, registrar-of-the-month – with incompatible UIs.
No audit trail for client changes
A DNS record broke something and nobody remembers who changed what. Registrar panels don’t keep proper history.
Bulk DNS changes are multi-hour work
SPF / DKIM update across 50 clients means 50 separate logins to 50 different panels.
Offboarding a client is messy
A client leaves and wants their DNS, but it sits under shared registrar logins – you can't hand over just theirs without giving access to everything.
What NexDNS gives an agency
Centralised DNS management built for multi-client workflows.
- Every client in one panel
- All client zones in one NexDNS account. Search and filter across every zone from a single login.
- REST API for bulk operations
- Update SPF on 50 client zones with a script. Add a CAA record everywhere.
nexdns applywith a YAML file does the whole fleet in one command. - Scoped API keys per integration
- Your Ansible playbook gets an API key scoped to
records.write. Your monitoring gets one scoped torecords.read. Revocable per-integration. - Full audit log
- Every zone and record change logged with who/when/what. Easy client accountability when something breaks.
- Zone export when a client leaves
- Export any zone to BIND at any time and hand the files to the client or their new provider – no lock-in.
- Terraform, OctoDNS, ACME plugins
- If you manage client infrastructure as code, NexDNS has the tooling. Terraform provider, OctoDNS sync, Certbot DNS-01 plugin included.
How agencies typically onboard
From first client import to standardised automation.
-
1
Create one NexDNS account for the agency
Starter works for up to 10 zones – usually enough to pilot with a handful of clients before upgrading to Pro or Business.
-
2
Import existing client zones
Export each client’s zone from their current DNS provider as BIND, then bulk import via
nexdns zone importor the panel. OctoDNS can sync from multiple sources simultaneously. -
3
Update NS records at client registrars
For each client, update NS records to point at NexDNS. Slave zones let you stage and verify propagation before the cutover. On the Business plan and above, you can use your own white-label nameserver hostnames instead of the NexDNS names.
-
4
Wire up automation
Terraform for new zone provisioning. CI/CD runs
nexdnsCLI commands for record changes. Certbot plugin handles wildcard certificates automatically. -
5
Build internal tooling
Add
nexdnscommands to your agency’s runbook. Document per-client conventions (NS group, DNSSEC policy, default TTLs) in YAML configs committed to git.
-
No – and that’s by design. NexDNS is your agency’s backend: your clients never log into NexDNS. You manage every client zone from your single account and expose whatever a client needs through your own tools. API keys are account-wide and built for your automation, so they can’t be handed to an individual client.
-
Yes, in two ways. Clone a fully configured zone (e.g. default MX + SPF + DKIM + DMARC for a managed email stack) to each new domain, or keep a declarative YAML of the standard records and roll it out across many zones with
nexdns applyor OctoDNS. Re-running apply keeps the matching zones in sync. -
The fastest path is OctoDNS with source providers for each. Point it at NexDNS as target and let it sync. For providers without OctoDNS support, BIND export +
nexdns zone importin a shell loop works for most cases. -
That’s exactly what the Terraform provider and OctoDNS YAML workflows are for. Define zone structure in code, commit to git, review via pull requests, apply via CI. Same workflow as Infrastructure-as-Code for the rest of your stack.
-
Export their zones to BIND, hand the files to the client or their new provider. If they’re moving to another NexDNS account, the export/import is a single CLI command. No platform lock-in.
Consolidate client DNS into one dashboard
Keep the automation hooks you already have.