On Fri, 2005-04-15 at 11:09 -0700, Bill Shupp wrote: > dopry wrote: > > On Fri, 2005-04-15 at 08:18 -0700, Bill Shupp wrote: > > > > > I would prefer not to have the service management available through > > Vega... I give my end users access to VegaDNS I wouldn't want them to > > have such control... > > It would be permissions based. The idea was this: > > VegaDNS can administer all aspects of DJBDNS. Add/Remove which IPs it > listens to, maintain dnscache settings, etc... > > Of course, this would be permissions based. But the idea was to make > djbdns so easy to administer, that it would encourage more people to > switch to it. But I certainly have the same reservations about allowing > such changes to be done over the web. That's why it has not been a > priority, and I'm not sure that it ever will be.
<snip> > > Why would you want to add/remove services from a running server, > > especially production? It would make sense for a general network/server > > administration tool that allowed you to provision services to servers > > or re-provision them as needed, but you would probably want to include > > FTP, HTTP, and email administration if you were working on such a tool. > > Perhaps. I'm not personally interested in managing all my services from > a web interface. However, as the designer of a djbdns web interface, I > thought it would be interesting to go the full distance with that > application only. > Even thinking about it... a compromise of the record database would be more a security issue than someone being able to disable the dns service via the web interface... Its easy to reinstall djbdns.... It can be difficult to replace a large DNS database, in a worse case scenario. > The emulation of SquirrelMail's plugin architecture in vHostAdmin is a > smart move, and could prove it a pretty popular tool in the long run. > I'm looking forward to seeing how it develops. > > Hmmm. Maybe I'll take more of a look at it. I couldn't find much documentation except a mention of it on the site, and what little there is in cvs. With that knowledge about the module/plugin system I may actually be able to get a working plug-in.
