Originally Posted by falko
You always have to create the slave zone in BIND. OTherwise BIND wouldn't know which zones to fetch from the master. It wouldn't even know the master.
Yes I know but I have created a Perl script that looks at the Mysql in mydns and creates the configs but I need a way to tie it into mydnsconfig and wondered if we couldn't help produce a version that works with mydns and bind slaves.
Basically I have a database table called "dns_slaves", then I have 3 columns for ns0, ns1, ns2
The values allowed are update or updated.
The Perl script looks at this table and if NS0 has a value of update, the Perl script does a select of the active domains and writes the configs and reloads bind. The script then changes this value for NS0 from update to updated. Xfers then takes of the rest.
What I wanted to get opinion was, if a domain was added/removed via mydnsconfig it would automatically update the dns_slaves table and allow the entire platform to be glued together for people who want to run mydns master with bind slaves.
Hopefully this all makes sense at this point. So basically we will have that perfect solution as I mentioned that works from one frontend.
Let me know or perhaps you can point me in the right direction of the files in mydnsconfig that I need to modify. I can then release it on the mydnsconfig site as a patch to help with bind slaves. It would be a shame not to share.