DNS infrastructure without the infrastructure
Offload DNS from your hosting stack. Managed nameservers, automatic DNSSEC, EU nameservers in two independent locations, and a REST API you can call from your panel, billing system, or provisioning code.
What’s costing you time today
Self-hosted DNS is an ops burden that grows with your customer base.
DNS server as a side business
Your DNS server needs patching, monitoring, and on-call coverage that has nothing to do with your actual hosting product.
DNSSEC is manual work
KSK and ZSK rotation, DS publication, NSEC3 salt updates – done by hand or by fragile cron scripts.
A single DNS server is a single point of failure
When your self-hosted DNS goes down, every client’s zones go with it. Multi-NS redundancy means more servers, more ops, more on-call – instead of time spent on your actual hosting product.
Redundant nameservers are more servers to run
Offering nameservers in more than one location means provisioning and maintaining another server, not just flipping a config.
What NexDNS removes from your plate
Managed DNS infrastructure your hosting customers benefit from – without any DNS ops on your side.
- REST API for custom integrations
- Zones, records, DNSSEC, account – every panel action has a documented REST endpoint. Call it from your hosting panel, billing system, custom portal, or provisioning script.
- Automatic DNSSEC on every zone
- KSK/ZSK generation, signing, rotation, and DS surface in the panel – all automatic. Every zone is signed by default; you handle nothing.
- Redundant EU nameservers out of the box
- Every zone is served from NexDNS nameservers in two independent EU locations (Germany and the Netherlands). No servers for you to provision.
- Scoped API keys for automation
- API keys are account-wide and built for your own automation – each one scoped to the operations an integration needs (zones, records, or webhooks; read or write). Name each key, set an optional expiry, and revoke it independently.
- Bulk zone operations via CLI and API
- Onboarding a batch of new customers is a single CLI command or a loop against the API. Clone a fully configured zone to each new domain, or roll a standard record set across many zones with declarative
nexdns apply. - Zone import/export in BIND
- Migrate an existing customer base by exporting from your current DNS and re-importing via
nexdns zone import– batch migrations with dry-run validation.
A typical hosting-provider deployment
Moving from self-hosted DNS to NexDNS, whatever panel you run.
-
1
Create a NexDNS account
Sign up, enable API access, and generate a scoped API key for your panel or provisioning scripts.
-
2
Build your integration
Call the REST API from your panel, billing system, or provisioning code. The zones, records, and DNSSEC endpoints are documented.
-
3
Migrate existing zones
Export your current DNS to BIND zone files and import via
nexdns zone import– bulk migrations with dry-run validation. Most panels have a BIND export option; the CLI supports batch processing. -
4
Update NS records at registrars
Change the NS records for your customers' domains to NexDNS nameservers (we publish the list in the panel). Stage with slave zones for zero-downtime cutover. On the Business plan and above, you can keep your own white-label nameserver hostnames instead of the NexDNS names.
-
5
Decommission the old DNS server
Run both systems in parallel until all NS records have propagated (TTL window), then retire the self-hosted DNS. One less server on your ops rota.
-
No. From the hosting panel they use, zone management works the same – your API integration or panel plugin abstracts the DNS backend. The only visible change is that DNSSEC starts signing automatically on new zones (and can be enabled on existing ones).
-
You publish new DS records at each registrar during cutover. NexDNS generates new keys and surfaces the DS record automatically – you update the DS at the registrar once per zone, and NexDNS handles all future rotations.
-
Your clients never need to see NexDNS. NS aliases let you publish zones on branded nameservers like
ns1.yourhost.net, so from the domain registrar to WHOIS, everything shows your brand. We bill you for your NexDNS subscription; billing your end clients stays on your side – we don’t provide a reseller-billing layer. -
All plans include support through our support desk during business hours – the same channel for everyone. We do not offer per-plan SLA tiers, named support contacts, or escalation paths. For custom zone and record limits, see the Enterprise plan.
-
Yes. NexDNS speaks the ISPmanager / DNSmanager XML API at
/dnsmgr, so you add NexDNS as a secondary DNS server in ISPmanager – no zone export, no workflow change for your clients. It’s a 2-minute config change. Full details on the ISPmanager integration page.
Managed DNS for your hosting customers
Plug into any hosting panel via REST API. Migrate customers on your schedule.