Will my zones behave the same as on self-hosted PowerDNS-Admin?

Yes – zones created through our panel, REST API, CLI, or ISPmanager endpoints behave exactly the same. The difference is where the servers live and who handles ops.

Can I keep using the PowerDNS HTTP API directly?

Not directly – you use the NexDNS REST API instead. For most use cases (CRUD on zones and records) it is equivalent, and we expose idempotent endpoints and API keys with granular scopes.

What about DNSSEC key rotation?

NexDNS handles KSK / ZSK generation and rotation automatically on Pro plans and above. You don’t run pdnsutil secure-zone, you don’t schedule rollovers, you don’t publish DS records manually – we do all of that, and surface the DS record in the panel for you to copy to your registrar once.

If I self-host PowerDNS-Admin today, how do I migrate?

Export zones with pdnsutil list-zone, import via our panel or CLI, verify via the propagation checker, then flip NS records at your registrar. DNSSEC requires a new DS record at cutover. Full walkthrough in the docs – see the zone-import guide.

Can I export my data back out if I want to leave?

Yes. Every zone can be exported as a BIND zone file from the panel or via nexdns zone export <domain> in the CLI. You can re-import that into PowerDNS-Admin, BIND, or any authoritative DNS server. No lock-in.

Managed DNS

NexDNS vs PowerDNS-Admin

PowerDNS-Admin is self-hosted. NexDNS removes the server, the panel upgrades, and the on-call rotation.

At a glance

NexDNS · PowerDNS-Admin

Deployment model: SaaS (fully managed)

Self-hosted (your servers, your databases)
Setup time: 2 minutes to first zone

Hours – OS, DB, PowerDNS, admin panel, DNSSEC keys
DNSSEC: Automatic signing on Pro and above, keys managed for you

Manual pdnsutil commands for KSK/ZSK, DS publication
Pricing from: 6.90 €/mo (Pro plan)

Free software + server + ops time

PowerDNS-Admin is a popular open-source web UI on top of PowerDNS, for teams that want full control of the stack and are comfortable operating DNS infrastructure. You install PowerDNS, install the admin panel, configure MySQL or PostgreSQL, handle upgrades of all three, roll DNSSEC keys, and monitor uptime. NexDNS delivers the same outcome as a fully managed SaaS with a purpose-built control panel, REST / ISPmanager APIs (Pro and above), and EU nameservers in two independent locations – the infrastructure PowerDNS-Admin lets you build, pre-built and operated.

Feature comparison

How NexDNS stacks up against PowerDNS-Admin across the dimensions that matter.

Capability	NexDNS	PowerDNS-Admin
Deployment model	SaaS (fully managed)	Self-hosted (your servers, your databases)
Setup time	2 minutes to first zone	Hours – OS, DB, PowerDNS, admin panel, DNSSEC keys
Maintenance	Zero – updates, backups, monitoring, DNSSEC rotation	You own PowerDNS + panel + DB patching, incidents, rotations
DNSSEC	Automatic signing on Pro and above, keys managed for you	Manual pdnsutil commands for KSK/ZSK, DS publication
API	REST API + ISPmanager / DNSmanager XML API compatibility (Pro and above)	PowerDNS HTTP API + admin-panel API
CLI tool	Official `nexdns` CLI, DNS-as-Code YAML	`pdnsutil` (CLI bundled with PowerDNS)
Terraform provider	Official provider	`pan-net/powerdns` (community, targets PowerDNS API)
ISPmanager compatibility	Full	None
Record types	A, AAAA, MX, CNAME, TXT, SRV, NS, CAA, PTR, ALIAS, TLSA, DS	All PowerDNS-supported types (ALIAS available in commercial PowerDNS only)
Pricing from	6.90 €/mo (Pro plan)	Free software + server + ops time

Choose NexDNS if…

You want managed DNS without running your own servers – managed updates, backups, and on-call
Your ops team is small and DNS is not their primary job
You want ISPmanager / DNSmanager API compatibility without writing the glue
You want redundant EU nameservers without provisioning and maintaining servers yourself

Stay on PowerDNS-Admin if…

You have on-premise / air-gapped requirements that forbid managed DNS
Your ops team already runs PowerDNS at scale and the self-hosted cost is amortized
You need a specific PowerDNS feature that only makes sense with direct database or pdnsutil access

Migrating from PowerDNS-Admin

Export each zone via pdnsutil list-zone <domain> to get a BIND-formatted zone file, then import into NexDNS via the panel or nexdns zone import <domain> zone.txt. DNSSEC keys don’t transfer – NexDNS generates new keys and publishes new DS records; you update the DS at your registrar during the cutover. Our CLI has a --dry-run flag that validates the import before applying.

Zone import guide Bulk import via CLI →

Frequently Asked Questions

The most common questions, answered.

Browse documentation

: Yes – zones created through our panel, REST API, CLI, or ISPmanager endpoints behave exactly the same. The difference is where the servers live and who handles ops.
: Not directly – you use the NexDNS REST API instead. For most use cases (CRUD on zones and records) it is equivalent, and we expose idempotent endpoints and API keys with granular scopes.
: NexDNS handles KSK / ZSK generation and rotation automatically on Pro plans and above. You don’t run pdnsutil secure-zone, you don’t schedule rollovers, you don’t publish DS records manually – we do all of that, and surface the DS record in the panel for you to copy to your registrar once.
: Export zones with pdnsutil list-zone, import via our panel or CLI, verify via the propagation checker, then flip NS records at your registrar. DNSSEC requires a new DS record at cutover. Full walkthrough in the docs – see the zone-import guide.
: Yes. Every zone can be exported as a BIND zone file from the panel or via nexdns zone export <domain> in the CLI. You can re-import that into PowerDNS-Admin, BIND, or any authoritative DNS server. No lock-in.

Managed DNS, without the servers

Start in 2 minutes – all the zones and none of the ops.