Re: dnsEditor [was: DLZ Web Management Interface]

Well, I know it has a long way to go - we manage about 900 domains
with it on a daily basis, and it was written specifically to fill a
need in our infrastructure.
My plan is to eventually rebuild it in django, but there a few things
I really want to have solved:
- I need some sort of user defined queries/views for CRUD to the
database, so the end user can use their own database format - one
option is to just require that some stored procedures exist, and use
those (obviously, this includes the ability to connect to multiple
backends).
- subdomains as separate records needs to be supported
- per domain/per records access control and authentication needs to be
implemented
- more/custom record types.  the main records types are supported,
including TXT, but some people need more, and sometimes need custom or
unique record types

and then, as you pointed out, an ajax search/paging or zones would be
necessary for any large amount of zones.

I am interested in developing it further, but just don't have much
incentive to right now, as it *works*, and it is at the point that it
covers all of our DNS management needs.  Not to mention, I always have
way to many projects going, so...

Lokkju

On Thu, Feb 14, 2008 at 12:44 AM, Jan-Piet Mens <[email protected]> wrote:
> Lokkju,
>
>  On Thu Feb 14 2008 at 08:43:53 CET, Lokkju Brennr wrote:
>
>  > https://svn.lokkju.com/svn/dnsEditor/trunk
>
>  It is very good looking and quite functional, but there are some things
>  wrong with it:
>
>  1. You load all the zones into a table in the browser; that works well
>    enough for a handful of zones, but try pointing the program at a
>    database with 100k zones in it ;-)
>
>  2. Unless I've overlooked something, there is no way to get additional
>    types into the database (SRV, etc.)
>
>  3. If the database contains other DNS record types, they are not
>    displayed.
>
>  4. There is something wrong with $cfg_primary_ns; PHP complains that
>    $primary_ns is undefined...
>
>  5. The button `update server' should be unnecessary; the provided shell
>    script dumps records and inserts them into other databases. People
>    will typically use MySQL replication for that...
>
>  Apart from that, you've done a great job, and it would be very valuable
>  if you could continue on it.
>
>         -JP
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/