DeepNet DNS Administrator

This is a DNS management tool I developed as a replacement for VegaDNS.

It closely follows the UI layout from VegaDNS's (apparently abandoned) 1.1.x development releases, but treats groups, domains, users, and domain records more uniformly. I also separated the group tree list from the operational sections.

It theoretically supports all DNS types (although actual support for deprecated or very obscure types is limited or nonexistent). Practically, A, AAAA, CNAME, MX, NS, SRV, and TXT records are supported. SOA records can mostly be altered but serial number schemes other than "let tinydns Do The Right Thing" are not yet supported (#24).

Data export to any front-end DNS server software should be possible; currently only export to tinydns is available.

Releases

v1.0 is finally released, after lurking in SVN for a while. Download the stable tarball from ​https://secure.deepnet.cx/releases/dnsadmin/.

Development on new features will continue on the trunk at ​https://secure.deepnet.cx/svn/dnsadmin.

Try out the live ​demo of v1.0 - full access is available using the default admin/admin user/password. Two other accounts are defined - test1 can create, edit, and delete domains and domain records; test2 is restricted to a subgroup, and can't make any changes. Use password test for either one.

Features

• Tree-based access scope control (users in subgroups can only see domains in that subgroup, and its direct children)
• Per-group default user permission and default record sets. Default records for a new group are cloned from the immediate parent group on creation.
• Per-user action controls - permission to add, edit, and delete groups, domains, users, or records can all be set separately.
• AXFR domain import
• WHOIS and DNS lookup tools
• Full internal activity logging

See the ticket list for features on the to-do list.

Requirements

• Perl
  • Standard modules:
    • CGI::Carp
    • Text::Wrap
  • Common non-core modules:
    • DBI
    • Digest::MD5
    • Net::DNS
  • Other modules:
    • CGI::Session
    • CGI::Simple
    • Crypt::PasswdMD5
    • HTML::Template
    • NetAddr::IP
  • Modules for RPC:
    • Frontier::Responder
• Postgres recommended; any database with real transaction support for all data manipulation could be used.
• Webserver supporting CGI executables.