Which versions of ISPmanager are supported?

ISPmanager 5 (Lite, Business) and ISPmanager 6 both work the same way. You add NexDNS as a secondary DNS server, which calls the same DNSmanager API on both versions.

What happens to zones already managed by my existing DNSmanager?

They stay where they are until you migrate them. The recommended path: add NexDNS to ISPmanager as a secondary DNS server, recreate the zones in ISPmanager (once you allow zone transfer from the NexDNS source IP on your primary, they transfer to NexDNS), update nameserver records at the registrar, and keep the old DNSmanager running read-only during the TTL window. Bulk imports via BIND zone files are also available if you have many zones.

How does ISPmanager handle errors returned by NexDNS?

ISPmanager surfaces NexDNS errors the same way it does with self-hosted DNSmanager: the same XML error format, the same notification path, and the same panel logs. Existing error-handling on the panel side keeps working.

Do I need to update nameserver records for my customers' domains?

Yes. After a zone is migrated, the domain’s NS records at the registrar need to point to the NexDNS nameservers (you can copy them from the NexDNS panel for the NS group you chose). Plan the change for a low-TTL window so propagation is quick. On the Business plan and above, white-label NS lets you publish zones under your own nameserver hostnames (e.g. ns1.yourhost.net ) instead of the NexDNS names, so the NS records keep your brand.

Can I keep slave zones I already replicate from another master?

Yes, on Pro plans and above. NexDNS supports slave zones with an external master, so a zone replicated from a registry server or another DNS provider can continue to be replicated through NexDNS without re-creating it as a master.

ISPmanager Integration

Full DNSmanager API compatibility – connect in 2 minutes

ISPmanager API

# ISPmanager sends to NexDNS:

POST https://api.nexdns.tech/dnsmgr?func=domain.edit

&name=example.com

&dtype=slave

&masterip=203.0.113.10

<doc>

<ok/>

</doc>

Replace DNSmanager with NexDNS – it takes just 2 minutes.

Connect to ISPmanager in 3 Steps

Create an Account

Configure ISPmanager

In ISPmanager, add NexDNS as a secondary DNS server with the login and secret from Account → Integrations.

Allow Transfer

On your primary server, allow zone transfer (AXFR) from the NexDNS source IP, then add a test zone to confirm.

Benefits of Switching

No server to manage

DNS runs entirely on our infrastructure. No installation, no configuration, no hardware to maintain.

Zero maintenance

No updates, no backups, no server monitoring – NexDNS handles them.

Better reliability

Nameservers in two independent EU locations (Germany and the Netherlands) with high-availability infrastructure.

More features

DNSSEC, DNS monitoring, import/export, and a modern control panel.

Frequently Asked Questions

The most common questions, answered.

Browse documentation

: ISPmanager 5 (Lite, Business) and ISPmanager 6 both work the same way. You add NexDNS as a secondary DNS server, which calls the same DNSmanager API on both versions.
: They stay where they are until you migrate them. The recommended path: add NexDNS to ISPmanager as a secondary DNS server, recreate the zones in ISPmanager (once you allow zone transfer from the NexDNS source IP on your primary, they transfer to NexDNS), update nameserver records at the registrar, and keep the old DNSmanager running read-only during the TTL window. Bulk imports via BIND zone files are also available if you have many zones.
: ISPmanager surfaces NexDNS errors the same way it does with self-hosted DNSmanager: the same XML error format, the same notification path, and the same panel logs. Existing error-handling on the panel side keeps working.
: Yes. After a zone is migrated, the domain’s NS records at the registrar need to point to the NexDNS nameservers (you can copy them from the NexDNS panel for the NS group you chose). Plan the change for a low-TTL window so propagation is quick. On the Business plan and above, white-label NS lets you publish zones under your own nameserver hostnames (e.g. ns1.yourhost.net) instead of the NexDNS names, so the NS records keep your brand.
: Yes, on Pro plans and above. NexDNS supports slave zones with an external master, so a zone replicated from a registry server or another DNS provider can continue to be replicated through NexDNS without re-creating it as a master.

Replace DNSmanager with NexDNS

NexDNS provides full compatibility with the DNSmanager API used by ISPmanager. Switch to a fully managed DNS infrastructure – no server to maintain.