1- A database of domains

We used LDAP with berkeley DB as backend for the domains database to store the domains and their name servers. The schema used is the dnszone schema.

2- A database of social information

For the social database, we also user the LDAP server to store social information which is the ower name,  the user password, the activation date , the expire date, the tech and admin contact of the domain, etc.
We wrote a schema for these informations with our OID(1.3.6.1.4.1.18250)

3- A zone file generator

For the zone file on the master name server , we used  LDAP as a backend  storage for zone file with the  patch for bind9 written by Stig venaas which is avalaible at http://www.venaas.no/ldap/bind-sdb/

4-An interface for the registry

For the database update and maintenance, we have a web based interface , which is used to manage the database. Any LDAP editor can also be used

5- An interface for the remote world

 For people outside of the registry who need access  to read and update the database,the same web based ldap editor inteface is used. They need a account which gives access read and write access to specific attributes.

Name servers

Our test name server run Fedora Core 1 with bind 9.3.

A ticketing system

we do not have one runing. registry is encourage to have one. Request Tracker  is recommended,but many other similar tools exist in free software.

A whois server and other information services

The whois server is a web based ldap client used to query the database about the social information.

it is avalaible here : http://annuaire.trstech.net/registry/search/search.php?server_id=0

search for domain name cafe or trstech.

Monitoring tools

Nagios is used to monitor the  servers and the services (named, openldap, web....).
it is available at : https://annuaire.trstech.net/nagios/  

readings