Session expiration Your session is going to expireClick here to extend


1,500 - 3,000

Posted on

2/27/13 11:45 PM



This project has expired

Why don't you register anyway? We are sure that you will find many similar projects out of the thousands waiting for you!

Post similar project now




Create a system based on PHP and MySQL w. multi-language interface. System represents a Sub-Domain Registry. Client Domains are registered as 3rd level domains under a set of existing 2nd level domains owned by registry.



User Registration & Management    

Domain Registration & Management    


DNS Management    

Admin Interface    

Invoicing & Payment    

Auto-Responder optional:    

Reseller & Affiliate Interface    

Support & Helpdesk



  1. User Registration & Management
    1. user can register and create an account
    2. use captcha image to prevent automated registrations
    3. use blacklist to ban registration from certain email providers, like,,, etc. (s. admin interface)
    4. user can log in, in order to register new domain names and manage his existing domain name registration (contacts, DNS, paments, and addl. services*)
    5. user ID is his email address
    6. password can be chosen freely but must respect a certain level of security (e.g.: a min. number of chars, CAPS, numbers, etc.)
    7. forgotten password can be sent by email upon request
    8. user data to be collected shall be :
      1. Handle (if known)
      2. (I)ndividual (R)ole
      3. Name (Last, First, MI)
      4. Organization Name
      5. Street Address
      6. City
      7. State
      8. ZIP/Postal Code
      9. Country
      10. Phone Number
      11. Fax Number
      12. E-Mail 
    9. account can hold multiply entities (e.g. for admin-c, owner-c, etc.) Key shall always be the respective email address
    10. assignment and management of unique handles. Handle shall be: [SERVICE-XYZABC-0107-000] (= name of service, users names initials, followed by month and years of the date when the handle was generated, a dash and 3 random digits).  
  2. Domain Registration & Management
  3. track users IP, exact time and date, browser-version used upon registration, referrer
  4. user can register new domain names
  5. user can modify and delete his existing domain names
  6. user can set up and edit for all domain names assigned to his account:
    1. edit NS records if he is using his own DNS (default)
    2. edit DNS info for A, MX, CNAME, IPv6-Addresses (AAAA-Record) and TXT records if he is using our DNS*
    3. edit SIP forwarding to be used w. his new domain name*. User is able to set the destination of calls.
    4. use dynamic DNS* (must use our DNS to use feature)
    5. URL Forwarding (cloaked and “normal”)* (must use our DNS to use feature)
    6. emailforwarding (limited to max. 30 email addresses per domain, max. size per email: 3 MB, max. 100 emails per day per address. Limits editable via Admin Interface)* (must use our DNS to use feature)
  7. allow registration of IDNs w. all characters defined in RFC 3492 and others. Conversion must be compatible w. all browsers (e.g. www.glü is encoded correctly, while www.glü is not compatible w. e.g. MSIE 6).
  8. allow simple and global edits (i.e.: allow him to modify the DNS for all his domains at once), domain locking and unlocking (locked domains can not be modified by user until unlocked), contact management, transaction history (e.g. all modifications made, renewals processed, etc.)
  9. provide possibility of bulk registration
  10. provide Wait Listing Service (WLS). With WLS, a registrar’s customers have the option to subscribe to a wait list for a currently registered domain name. If the domain name becomes available during the subscription term, the customer receives the registration automatically. WLS is not publicly accessible as intended for dispute resolution   
  11. make WHOIS data accessible via commandline and webpage
  12. imply security measures in order to prevent robots from collecting data (e.g. captcha image on web frontend)
  13. allow queries for handles assigned by us, for domain names that were registered w. us, for domain names under all existing TLDs and for IP-Numbers
  14. allow admin to filter lines of WHOIS data received from other WHOIS Servers for domains not within our 2nd level domain names
  15. allow admin to add WHOIS data for domains not within our 2nd level domain names   
  16. build system based on “PowerDNS” or any other similar product. Hold DNS data in MySQL Database instead of zonefiles, but keep it compatible w. BIND style secondairies.
  17. allow up to 10 nameservers per domain
  18. allow user to use our nameservers*
  19. restrict xfer to specified secondairies in order to prevent unauthorized entities to download entire zones 
  20. As the whole system is to be template based, the admin can modify the look of all pagesn via the admin panel
  21. admin is able to set defaluit language
  22. admin can add/remove the 2nd-level domains, under which registartion is offered
  23. admin can create, edit, delete, modify domain name registration and user data
  24. admin can re-send resp. re-generate original invoices and reminders or send modified invoices
  25. admin can edit payment information (set domain status (connected, on hold, dispute, paid till, etc.)
  26. admin can change prices for all features offered (incl. setting diff. prices for diff. domains)
  27. admin can move domains from/to diff. users and reseller-accounts
  28. admin can set a “usual” user account to a “reseller” account
  29. admin can acknowledge payments received in context w. “Business Partner Program”.
  30. admin can ban individual IPs, IP Classes, eMail Providers and countires (via GeoIP) from using the service. Banned entities are forwared to a certain "bogus" error page   
  31. there are basically 2 payment methods:
    1. instant online payment via Credit Card at moment of domain name registration through 2 processors: and Paypal. Process their servers feedback and generate/display a payment status instantly to user.
    2. within 30 days after the user received the invoice, either online, or cash or banktransfer.
    3. accept online payments, even if banktransfer was initially chosen.
  32. allow user to re-new his domain name registration at any time for any period offered (1,2,3,5,10,99 years)
  33. allow user to buy addl. services at any time for any period offered.
  34. invoices are sent our as .pdf and text and kept in database for later retrieval by user and/or re-seller and/or admin
  35. 30 days after invoice is submitted and no payment was accounted for, send "Final Notice" to Billing-c
  36. 10 days after final notice, send deactivation notice to all contacts and deactivate domain "(change status to: "on hold")
  37. 30 days after deactivation notice remove domain from database and make it available registration again
  38. 30 days before expiration of domain name, send invoice for renewal to billing c (proceed as 6.3)
  39. allow admin to set status of a domain name registration to “paid” when a payment via banktransfer is received
  40. allow admin to set status of a domain name registration to “un-paid” if a payment is contested (CC chargeback, etc.)
  41. “Business Partner Program” w. prepaid, discounted registrations (see below).
  42. allow conditions (via admin interface) e.g. diff. VAT for diff. countries, diff. texts for diff. destinations, etc. (Example: If billing-c is in Nigeria, do not send invoice to billing-c, just to service accounting).  
  43. autorespond to all emails to "[OBSCURED]" w. a certain static text
  44. include a quote of the senders original message
  45. assign tracking number. Examples: [SERVICE[OBSCURED]3] or [SERVICE[OBSCURED]3] etc. which is: Shortcut for the entity addressed, date when email was received, a dash and a 3 digit random number.
  46. make auto-responder sensible for bouncing auto-replies e.g. w. other auto-responders (e.g.: do not submit more then 5 auto- responses to 1 sender within 10 minutes, do not submit more then 30 auto-responses to 1 sender per day, do not reply to mailer-errors, mailer-daemons, etc.
  47. make auto-responder “spam-aware” (e.g. let him work “behind spam-assassin”)
  48. keep editable blacklist in order to manage who will never get a auto-reply from hostmaster
  49. forward incoming emails and auto-replies to hostmaster's POP3 account.
  50. parse for domain template: if emails contains valid template, process as registration, modification or deletion.   
  51. Mandatory: "Business Partner Program". Resellers that register larger amounts of domains can set up a business account by making a one time payment. Registration fees are then debited from their credit. Free discounts can be applied by admin by e.g. adding 3.900,- EUR to an account that actually received a 3.000,- EUR payment, granting an effective 30% discount.
  52. Optional: Affiliates can register account. Provide unique link to be implemented on Affiliates website to track all leads that result in a successful domain name registration
  53. create a level above the user level that can manage the user accounts assigned to it
  54. create an API that is compatibile w. enom.  
  55. create a ticket management system based on php/mysql
  56. user can enter w. his account data in order to submit a trouble ticket
  57. system (="engine") to be accessible over diff. frontends / domains in order to support various services
  58. tracking number is assigned to each ticket. Format varies w. the site the ticket is referring to. Examples: [SERVICE1- TICKET#[OBSCURED]] or [SERVICE2-TICKET#[OBSCURED]] etc. which is: Shortcut for the entity concerned, date when ticket was opened, a dash and a 3 digit random number.
  59. copies of tickets are sent to user and admin when a ticket is opened, modified or closed
  60. WHOIS
  61. DNS Management
  62. Admin Module
  63. Invoicing & Payments
  64. Auto-Responder
  65. Reseller & Affiliate Interface
  66. Support & Helpdesk (optinal)


*) additional fees apply for the user.