Migrating DNS records to ISPConfig3

Hello,

We are going to be migrating DNS records from a remote name server to some DNS we are setting up in ISPConfig3. The remote server is running PowerDNS, so there are not zone files, per se.

We had previously brought DNS records into the PowerDNS a different provider's name servers by doing the following:

1. Set the "Allow Transfer To" setting on the domain record at the reote provider to allow the IP address of the PowerDNS server we were importing into
2. Add the domain we wanted to migrate in to PowerDNS and create it as a "secondary" zone, and putting the IP address of the remote provider's DNS as the master
3. Once record was imported in to PowerDNS, change the record from being a "secondary" zone to a "master" (this was a simple dropdown)

I am hoping to be able to do something similar here, with our Bind-backed DNS servers but doing the following:

1. Create the domain we want to migrate as a secondary zone and the PowerDNS server as the master
2. When the domain is created (as a secondary), update the named.conf.local file so the domain is changed to a "master", remove the "masters" IP entry, and change the name of the file to pri.domain.tld and restart Bind.

I did a test of the above steps, but it seems that the zone file that gets created for a secondary zone is in a bit of a binary format, rather than the "normal" Bind format that a master zone file is created as, but I am able to convert it using named-compilezone. I then also updated the named.conf.local to make the zone a master, but of course it does not show up in the list of (master) zones. Is there an inherent way to get ISPConfig3 to pick that zone file up as a master (after that second step) and display it as such, or am I likely going to have to do an extra step of downloading the converted zone files then just do "Import Zone File" (and then of course delete the secondary zones in ISPConfig3)?

 

I worte a script for our migration that extracted the information from the old database and then made use of the remoting API of ISPConfig to import all the zones are records. That requires some scripting on your end but it might be an easy solution for you aswell.