Hey all! Almost 100% complete in my quest to convert from my old self-maintained hosting setup to using ISPConfig to drive it all. The only thing I have left is to make it so I can have my slave DNS server taking updates from ISPConfig. The way I have things right now in my self-maintained setup is all my zone directives for bind are in a separate file included from named.conf. I also have a perl script which parses this file, switching those zones from a master config to a slave config, then copying the resulting file over to the slave DNS server via a key-based SCP command. A reload is then triggered on the slave so it pulls the new zone over from the master. Has anyone ever set up something similar with the ISPConfig DNS structure? Maybe even so far as to tie it into the domain creation routines so it's done automatically? I haven't put ISPConfig into control over my DNS yet because of this issue, and it's the last thing I have to figure out Thanks, Jeremy
Do you use BIND on your second server? Then yu simply have to add something like Code: zone "example.com" { type slave; file "sec.example.com"; masters { 1.2.3.4; }; }; to your named.conf and restart BIND. Replace example.com with the real domain name and 1.2.3.4 with the IP address if your ISPConfig server. The BIND on the ISPConfig server will then do a zone transfer to your secondary DNS.
falko, The sec.example.com can be the same file of pri.example.com? I wrote this in other thread (http://www.howtoforge.org/forums/showthread.php?t=5004): I have one IP. I use a service like No-IP to make my Secondary DNS Server. But now I have a friend with one IP too, and the same solution (No-IP). I have to only put the allow-tranfer {ip} and nothing more? And the zones in the named.conf? And pri.xxx files? Thanks all, Vinicius
I made my setup in this weekend... Is so simple... Thanks again. Always you have a good answer... I read with attention the Tradiocional DNS How-To, I learn a lot of things... I should read this text before. Vinicius