jlasman said:
If you're aware of any system built into BIND that enables it to tell another server to slave it's zones, please tell me. Also please tell the bind developers at isc.org.
They assure me that there is no method built into BIND that allows one BIND server to tell another BIND server which domains to slave.
You misunderstand me. Surely you know of the Bind notification system... where if a domain name has a slave zone on the secondary DNS server, the secondary DNS server will look out for new serial numbers and mirror the settings of the master zone. It's how I have my slave DNS configured.
jlasman said:
My system is a simple one, to tell BIND servers what domains to slave.
Sure, you can easily log into multiple systems and tell them what domains to slave if that's what you want to do.
Please
read my posts. I am suggesting that DA code a small daemon which can run on a secondary DNS server, and listen for updates from the main DA server. DA can use some kind of remote access key or authentication system to interact with the DA-coded daemon on the secondary DNS server, and notify it which zones/domains to slave.
jlasman said:
Or you can have DA do it for you.
I fully intend to have DA do it for me... rather than using some complex scipt plus FTP system. Not to mention the fact that FTP is unsecure, so someone could steal the password and upload any DNS data they liked.
jlasman said:
And how would it know which domains to add? You've got have a way to communicate between the two servers. My method (thought out by several people in brainstorming sessions) works simply, and it works whether you've got multiple DA systems, or other systems (Plesk, RaQ, CPanel, H-Sphere, etc.), or even stand-alone systems.
See my comments above... the domains to add would be communicated securely to the mini-DA daemon.
jlasman said:
But maybe my system is too complex (for example, it allows for continued slaving of systems that disappear from the 'net). Please come up with a better one; I'm certaily willing to listen, and that's the beauty of open source projects; if you don't like what I'm doing, please do it better.
I appreciate your project, but I simply think that for DA (and remember we are in a DA forum, not a Bind forum), then we should use a DA daemon. If people want to use your scripts, they could simply disable the DA option and use your script instead... no biggie.
jlasman said:
I hope the DA staff will consider my ideas; if they don't, then that's okay, too. Since most members of the open source community who have to slave DNS aren't running DA, there's still quite a bit of interest in my idea.
Jeff, again, I don't doubt that people like your idea. My point is that from the tone of your posts, it seemed as though you want your script system to be implemented as a standard DA install, rather than havingJohn code a more secure and less complicated solution (IMHO).
I could release my PHP too as open-source, add authentication schemes to it etc, and it would add domains to be slaved to the secondary DNS server securely and automatically. But I doubt DA would want to use it... unlike other control panels, DA is hardcoded in C and seems to avoid scripts where possible. I'm positive that DA wouldn't want to use my script either. It's not your script that I'm pulling apart, it's the idea of using it as the official DA solution to slave DNS.
jlasman said:
Just like my SpamBlocker and VirusChecker, use them or not, as you see fit.
People will be able to choose to use them, but I don't think that your slave DNS scripts should be the official DA solution, as your earlier posts suggested.
jlasman said:
As I wrote above, that daemon has to get the list of domains to slave somewhere. It has to communicate over the 'net. If you and/or DA staff want to implement some proprietary to DA method rather than an open source method, that's fine with me.
[/B]
I know it needs the list of domains - it'd receive them from the main DA server. I'm not suggesting my method is fullproof, I'm sure John will have a much better idea... I just don't think your solution is the answer for DA.
If you need a secondary DNS server which can receive notification from several control panel systems, I don't see why the DA mini-daemon couldn't work with your script.
I hope you understand my view Jeff, please do read everything I've written. It's not an attack on your script, but I'd rather not see such a solution introduced on my DA server. I'd like it to be much simpler, and more secure.
Best regards,
Matt
.
