So I read a lot of posts saying you can setup a second bind box, running ISPConfig, but I don't see how you get the two to know about each other. And automatically, when you setup a "web" create the appropriate slave on the secondary for you. Though I'm versed in DNS/bind config and could easily setup the secondary to slave from the primary, if ISPConfig likes to overwrite you config (so I read), then I'm assuming you wouldn't want to do that. My goal: when creating a new web (including any resellers) the primary and secondary is auto filled in and created appropriately.
1) Install two dns servers. 2) Create a primary dns record for a domain on server one. 3) Create a secondary dns record for the domain on server two. Bind will now sync the dns details to the second server and keep the data up to date.
See, the point is I want to skip step 3. I shouldn't have to touch the secondary. Rsync/scripts could do this, I'm wondering what other's have done.
right, cause ISPConfig will overwrite it, so is there a way of making one ISPConfig box automagically know of and configure another?
is there solution for secondary master DNS / BIND without ispconfig ? something like... crone on secondary master DNS every 2-3 hours check if there is change in database, and if it is - generate conf and zones on secondary master tnx
