... | ... | @@ -23,12 +23,27 @@ The ideas list below is intended to provide you with starter ideas for GSOC proj |
|
|
**Requirement**:
|
|
|
BIND is under active development, with new releases issued frequently. It is not uncommon for organizations to maintain dozens of BIND servers and for some of them to be very infrequently updated. This would provide a new service for the BIND administrator, to query their BIND 9 server, which would then check (some undefined service) at ISC or the packager, and reply back whether the BIND 9 version is current and up-to-date or needs an upgrade.
|
|
|
|
|
|
**Deliverable**:
|
|
|
**Deliverable:**
|
|
|
The entire feature would require code committed to BIND to add the command grammar, and to implement the lookup, a design for the backend service which will reply back to the server, documentation for the feature, and outreach to the BIND User community.
|
|
|
Any feature that 'phones home' to get information will automatically be somewhat suspect and so development of this feature would need to be particularly transparent, and carried out with user input.
|
|
|
|
|
|
**Skills required:** ...
|
|
|
|
|
|
**Mentor:** /
|
|
|
**Complexity:** uh, medium?
|
|
|
|
|
|
**Complexity:** uh, medium? |
|
|
\ No newline at end of file |
|
|
**Mentor:**
|
|
|
|
|
|
|
|
|
### 2. Implement a zone database for BIND, using the existing dyndb API.
|
|
|
|
|
|
**Requirement**
|
|
|
ISPs often provide a graphical web interface for requesting and enabling new domain names for their users. They may have a very large number of very small parked or 'vanity' domains, with many new and changed domains, which are queried relatively infrequently. It is ideal to maintain these zones in a separate database, which the ISP can easily develop a provisioning front-end for. In BIND 9.11.0 we added a new api, the Dyndb api, which is designed for exactly this purpose. So far, however, the only known database implementation of the API is for the RedHat FreeIPA service.
|
|
|
|
|
|
**Deliverable:**
|
|
|
Select a reasonably popular, easy to use and well-supported existing open source database. Ideally, contact the maintainers of this database and let them know you are planning to work on this project. Implement an appropriate schema for a BIND zone file in the database. Implement a service interface for the BIND dyndb api. Integrate the two, and verify that you can serve a zone in the database via a query to the BIND instance. Write some basic documentation on how to use the feature and any new commands required.
|
|
|
Post the database code somewhere it can be easily found by BIND users (we will help with this) and also submit it back to the upstream project, as appropriate and depending on the interest of the upstream maintainers.
|
|
|
|
|
|
**Skills Required:**
|
|
|
|
|
|
**Complexity:** Ambitious
|
|
|
**Mentor:** |
|
|
\ No newline at end of file |