I in theory would like webmin for this in a fast and dirty development environment, but it still has too many infosec problems for my taste for production.
In the past when I had the time and work driven focus to harden webmin with only custom module which all used sudo for an appliance I was able to reconcile my issues, but in production as is it stock webmin is risky. Many if these concerns could be handles by selinux now but the webmin developers are still behind the ball on writing the appropriate rules or even requiring module writer to include the prerequisite rules so I still wouldn't consider it in production.
-- Sent from my HP Pre3
On Jan 9, 2014 19:50, Nico Kadel-Garcia <[log in to unmask]> wrote:
BIND for the server, "webmin" for the configuration tool. and my
presentation at SVNday a few years ago if you wnat notes on how to put
it under source control.
Don't forget "mkrdns" for generating your reverse DNS reliably: the
RPM building tools are at
https://github.com/nkadel/repoforge-rpms-nkadel-dev/tree/master/specs/mkrdns/
On Thu, Jan 9, 2014 at 7:26 PM, Steven Haigh <[log in to unmask]> wrote:
> On 10/01/2014 11:16 AM, Jeremy Wellner wrote:
>> I've been using BIND on RHEL5 for years and it's come time to overhaul
>> those venerable DNS boxes.
>>
>> I've seen alot of alternatives like NSD, PowerDNS, YADIFA, and others
>> but I'm wondering what experience has been with going to something other
>> than BIND.
>>
>> Having a database backend is very attractive, but so is having a
>> manageable GUI for those in the department that work with adding devices
>> and are scared of text files and the black of terminal.
>
> Use bind. DNS is all about reliability - not pretty or GUIs...
>
> --
> Steven Haigh
>
> Email: [log in to unmask]
> Web: https://www.crc.id.au
> Phone: (03) 9001 6090 - 0412 935 897
> Fax: (03) 8338 0299
>