Replace new_password with a secure password. It will be used to grant MyDNS read-only access to the record database; this ensures that no exploits can result in write access to the record store (it is recommend that you setup another MySQL user for scripted write access to the database).

Next, import the default database:

mydns --create-tables | mysql -u root -p mydns

The last step is to adjust the MyDNS configuration file to use the newly database user credentials:

Start the service

MyDNS is now fully configured and ready to run. The service can be started:

service mydns start

Administering the server

MyDNS will now serve records zones from the rr with records from the soa table. The daemon does not have to be restarted for changes to be recognized, so you can take advantage of this by using scripts to update your MyDNS database on-the-fly. Zone replication via SQL backups is another particularly handy side-effect of this feature.

As an example, included below is a small script I use to add new domains my servers:

As you can see above, it adds a zone for each domain and then sets up default CNAME aliases for www and mail to point to the main domain. The main domain gets pointed at the default shared IP using an A record.