The bind setup is based on config files and not on a mysql database, this makes switching to bind a bit more complicated. If you want to switch form mydns to bind, you have to uninstall mydns, then install bind, then run the ispconfig update.php and select to reconfigure services. Then go to the ispconfig server settings and check that the path for the named.conf file and the directory for the bind config files is correct. Afterwards you will have to edit every dns record (zone) in ispconfig, change a value like the ttl and click on save, so that the bind files get written for this record.

Thanks for the information, I did the following and it appears to have worked as expected:

Deleted myDNS from the server and removed from startup directories
Restarted server
Installed Bind9
Downloaded ISPConfig and ran update.php
Logged in to control panel and checked DNS settings under the Server Config menu, they were all correct
Edited DNS record to trigger an update
Manually checked the bind directory and the new DNS file was created

It looks as if everything worked and the new Bind DNS server is responding to requests for the domain names it hosts.

The only reason I wanted to switch was just as an experiment to see how I could do it.

Mydns works perfectly for me but I have a test server that I use to play about with as I find it a great way to learn how things work, if it all goes wrong I can just blank it and start again from scratch.

To remove mydns I just did a search on the hard drive for files called mydns and deleted them then went in to the rc[0 1 2 ...].d directories and removed the mydns files (this prevents mydns from starting on boot). I then restarted and installed bind9 and then edited all my dns zones as recommend by Till.

After this bind9 had all the required data in its zone files and was working as expected.

I have a question: You downloaded MyDNS tar.gz package ( 1.2.8.27 2009-03-26 ) or maybe files from SVN? I noticed that although tar.gz package was released more than year ago, there was changes in SVN (e.g. http://mydns-ng.svn.sourceforge.net/viewvc/mydns-ng?view=rev&revision=217 and before). One of rev should fix problem with axfr (from description). So tell me if you used SVN and this is the reason why it works for you but not for me.

When you download ISPConfig3 again (since it is no longer in your /tmp directory) and look in the 'install' directory, you will find update.php as well as all the other scripts for manipulating your ISPConfig3 installation.

No, it will not hurt your system even if you were to invoke the install.php script. It would just tell you ISPConfig3 is already installed and to try update or upgrade so no harm would be done anyway. All you are doing is repopulating a directory with the files needed to install, upgrade, or update your ISPConfig3 installation

I am not totally sure (can't recall) but if it follows the scenario for the OS update you would first run that command and then upgrade. Update seems to gather the info about the availability of updates and Upgrade does the actual install.

So, while in the install directory.... do php -q update.php and then php -q upgrade.php. I am almost certain that is what I did.

To be honest, I don't know about the -q. I was trying to find out what that option means but I couldn't find it anywhere. I know I ran it on my machines without any problem but I would like to know what the option '-q' is all about.

Ok i have done the migration to bind. Zone files have been created successfully in /etc/named.d also zone files are listed in /etc/named.conf.include but the name server does not respond to the requests.

Forwarders seem to work only from the same machine (the server itself).

The bind setup is based on config files and not on a mysql database, this makes switching to bind a bit more complicated. If you want to switch form mydns to bind, you have to uninstall mydns, then install bind, then run the ispconfig update.php and select to reconfigure services. Then go to the ispconfig server settings and check that the path for the named.conf file and the directory for the bind config files is correct. Afterwards you will have to edit every dns record (zone) in ispconfig, change a value like the ttl and click on save, so that the bind files get written for this record.