[Pdns-users] GUI survey

[John Miller]

Thanks to everyone who's responded thus far.  Please keep the responses 
coming!

Right now we're looking pretty hard at poweradmin and 
django-powerdns-manager.  poweradmin has some interesting bugs (that 
we'd probably fix); django-powerdns-manager doesn't do all we want it 
to, but what it does, it does well.  We like Python, and since the 
project's based on Django, the code is easy to follow.

May give JPowerAdmin a second look, though we don't speak much Java.

John

On 02/04/2013 09:06 PM, John Miller wrote:
> Hello everyone,
>
> As we get ready to roll out PowerDNS for our authoritative nameservers,
> I'm evaluating the GUI gamut to see what's available and works well.
> I've installed dev copies of just about every GUI listed in the wiki.
> There's drawbacks to just about all of them (unwieldy interface, no
> DNSSEC support, no support for groups, no domain templating system,
> buggy code, manual PTR maintenance), and quite a few seem to no longer
> be maintained (last commit older than a year).
>
> What are folks using?  What databases are you running on the backend?
> Any particular things you do/don't like about your choice?  If you're
> running custom code, why (and can I have a copy)?  I know there's tons
> of older posts talking about GUIs, but I think it'd be valuable to bring
> the discussion up to date.
>
> If I could find something to do the following, I'd be grinning like
> PowerDNSTango's Cheshire Cat:
>
>   * Login via SSO and/or AD/LDAP
>   * Group assignment via AD/LDAP
>   * Auto-update PTR records
>   * DNSSEC support
>   * Relatively quick loading
>   * AJAXy sort and search capability
>   * Change logging
>   * Integrity checking for all record types
>   * Skinnable interface
>   * Domain/zone Templates
>   * "Create subdomain" ability
>   * Role-based access
>   * separation of gui database from main PowerDNS database
>   * supports multiple PowerDNS databases and/or views, multiple SQL users
>   * auto-increment serial numbers
>   * some form of revision control/rollback
>   * remote API (REST, XML-RPC, SOAP, etc.)
>   * basic server monitoring and statistics
>   * allows non-RFC TLDs for internal DNS
>   * visual separation of forward and reverse zones for ease of editing
>     (when you have 10 forward and 200 reverse zones, separation is a
>     good thing).
>   * native, master, and slave support
>