PowerDNS Admin Web Frontend
From Linuxnetworks
Revision as of 15:32, 20 December 2007 by 212.60.138.116 (Talk)
Also, there are a few existing web-based tools for administrating PowerDNS installations, none of them seem to be good enough for daily work, especially where access for end-users is required. This page should be a starting point to collect requirements from users to describe the needed features for a PowerDNS administration web frontend.
- Should be able to work with SQL, LDAP and file based backends
- SQL backend should handle all supported databases
- Check all existing record types for correctness
* Disallow duplicates * Disallow CNAME and other RR
- Support multiple site owners which can change their own records
- Completely skinable templates for different CIs
- Use PHP > 5.1
- Nice design
- Must allow working with lynx/w3m on text consoles (e.g. W3C WAI-CSS-stylesheet)
- XHTML-1.0-strict validation
- Optional AJAX to make it "look good"
- Allow "paging" through database when it contains many thousands of zones/records
- User-management should be "under" web server (i.e. use Apache authentication methods)
- Object-oriented programming
- Model-View-Controller architecture
- Dialogs for complex records creating IANA specs/RFC based syntax (e.g. user selects NAPTR-RR and gets a drop-down box with the list of IANA protocols and a text field for the URI. The dialog function then creates the complex syntax of the NAPTR-RR).
- Record types:
* A * AAAA * MX * NS * PTR * TXT * HINFO * SRV
- DynamicDNS interface (HTTP-based like dyndns.com)
Please add your own suggestions to this list or add your comment to the discussion page if you are unsure.