Difference between revisions of "PowerDNS Admin Web Frontend"
From Linuxnetworks
(reorg) |
|||
| Line 1: | Line 1: | ||
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. | 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 | + | General: |
| + | * Web-based interface | ||
| + | * Should be able to work with SQL and LDAP based backends | ||
* SQL backend should handle all supported databases | * SQL backend should handle all supported databases | ||
| − | * | + | * DynamicDNS interface (HTTP-based like dyndns.com) |
| − | + | ||
| − | + | Authentication/Authorization: | |
* Support multiple site owners which can change their own records | * Support multiple site owners which can change their own records | ||
| + | * User-management should be "under" web server (i.e. use Apache authentication methods) | ||
| + | * Support different authentication and access control sources (database, LDAP, HTTP Auth, etc) | ||
| + | |||
| + | DNS records: | ||
| + | * Support creation of all record types | ||
| + | * 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). | ||
| + | * Check all existing record types for correctness | ||
| + | ** Disallow duplicates | ||
| + | ** Disallow CNAME and other RR | ||
| + | |||
| + | Usability: | ||
| + | * Allow "paging" through database when it contains many thousands of zones/records | ||
| + | |||
| + | Templates: | ||
* Completely skinable templates for different CIs | * Completely skinable templates for different CIs | ||
| − | |||
| − | |||
| − | |||
* Nice design | * Nice design | ||
| − | + | ||
| − | + | Techniques: | |
| − | + | ||
| − | + | ||
* Object-oriented programming | * Object-oriented programming | ||
* Model-View-Controller architecture | * Model-View-Controller architecture | ||
| − | * | + | * Optional AJAX to make it "look good" |
| + | * Use PHP > 5.1 | ||
| + | |||
| + | Standards: | ||
| + | * XHTML-1.1-strict validation | ||
| + | * CSS 2.1 validation | ||
| + | * Must allow working with lynx/w3m on text consoles (e.g. W3C WAI-CSS-stylesheet) | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Please add your own suggestions to this list or add your comment to the discussion page if you are unsure. | Please add your own suggestions to this list or add your comment to the discussion page if you are unsure. | ||
Revision as of 00:45, 21 December 2007
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.
General:
- Web-based interface
- Should be able to work with SQL and LDAP based backends
- SQL backend should handle all supported databases
- DynamicDNS interface (HTTP-based like dyndns.com)
Authentication/Authorization:
- Support multiple site owners which can change their own records
- User-management should be "under" web server (i.e. use Apache authentication methods)
- Support different authentication and access control sources (database, LDAP, HTTP Auth, etc)
DNS records:
- Support creation of all record types
- 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).
- Check all existing record types for correctness
- Disallow duplicates
- Disallow CNAME and other RR
Usability:
- Allow "paging" through database when it contains many thousands of zones/records
Templates:
- Completely skinable templates for different CIs
- Nice design
Techniques:
- Object-oriented programming
- Model-View-Controller architecture
- Optional AJAX to make it "look good"
- Use PHP > 5.1
Standards:
- XHTML-1.1-strict validation
- CSS 2.1 validation
- Must allow working with lynx/w3m on text consoles (e.g. W3C WAI-CSS-stylesheet)
Please add your own suggestions to this list or add your comment to the discussion page if you are unsure.
