AusRegistry's Technical Accreditation

The following information is intended to familiarise interested parties with AusRegistry's requirements for Technical Registrar Accreditation.

The technical accreditation process cannot commence until interested parties have been provisionally accredited by auDA, the .au Domain Administration. Please contact auDA at www.auda.org.au for further information.

In order to receive technical accreditation from AusRegistry you will be required to perform the following primary functions:

The ability to perform the above functions will be tested in two parts:

  1. Part A tests your technical abilities in either category: EPP Protocol or via the Registrars Administration Interface (Web)
  2. Part B AusRegistry uses a checklist to test your system's registration and management tools to see if all functions are available and operational

It is important to note that whilst becoming a technically accredited registrar is a relatively straight forward process, it does however require a large amount of time and effort to build a comprehensive registration system. (This is dependant on the level of efficiency you wish to achieve).

With strong competition amongst all Registrars, the efficiency of your systems will vastly affect your success as a Registrar.

EPP

The protocol used to interface with the Registry is the IETF's EPP version 1.0 protocol.

The documents below will provide you with all the details of the protocol:
RFC 3730: Extensible Provisioning Protocol (EPP)
RFC 3731: Extensible Provisioning Protocol (EPP) Domain Name Mapping
RFC 3732: Extensible Provisioning Protocol (EPP) Host Mapping
RFC 3733: Extensible Provisioning Protocol (EPP) Contact Mapping
RFC 3734: Extensible Provisioning Protocol (EPP) Transport Over TCP
RFC 3735: Guidelines for Extending the Extensible Provisioning Protocol (EPP)

A Registrar must also have a good knowledge of:

  1. The DNS system (see below: RFC1034, RFC1035, RFC1101, RFC2181, RFC2182 and RFC3007)
  2. The use of Name Servers
  3. What a Glue record means
  4. The Registry-Registrar model
  5. WhoIs protocol (see RFC-954) and its intended use. (Please Note: This is not for the lookup of Domain Names, EPP provides procedures by which the availability of a domain name can be checked.)
Relevant RFC Files are located here:
RFC 954: NICNAME/WHOIS
RFC 1034: Domain Names - Concepts and facilities
RFC 1035: Domain Names - Implementation and Specification
RFC 1101: DNS Encoding of Network Names and Other Types
RFC 2181: Clarifications to the DNS Specification
RFC 3007: Secure Domain Name System (DNS) Dynamic Update

In order to complete the above functions AusRegistry has developed two interfaces, an EPP based protocol interface and an HTTPS based administration web site. Use of either interface is dependant on a Registrar's volume of sales and their technically capabilities.

Part A - Technical Abilities

Registrars must pass a technical abilities test in AusRegistry's OT&E environment. A test is available from each category below.

  1. Registrars Admin Interface
    The Admin interface is a web site based around the EPP protocol implemented by the Registry. It provides a manual method of performing the commands on the Registry. This manual process is relatively time consuming compared to the protocol method and impracticable for those processing large amounts of registrations. It also provides domain reports, accounting reports, and the ability to manage registrar passwords.

  2. EPP Protocol
    The Registry also offers a standard EPP version 6 compliant SSL base server. To ensure a smooth connection process to this service. AusRegistry provides a range of toolkits available in C++, Perl, and Java versions. The Java toolkit will run on both Windows and *nix platforms. The C++ and Perl is currently only supported on *nix platforms. Registrars are also free to develop their own custom interfaces to the Registry using the EPP protocol directly. These interfaces need to be fully EPP version 6, and SSL compliant (see IETF drafts referenced above) to function correctly with the Registry.

    When connecting to the Registry in this fashion Registrars are able to provide quick turnarounds of Domain Name registrations and fully automate their entire systems. Note: Any Registrar who passes the OT&E certification at this level is automatically qualified to use the admin interface described above. The suggested method for constructing a Registrar system using these toolkits is to keep a client side database. This will be updated by your web scripts. Then, a job is run that reconciles the changes in your database with the Registry. Which ever method you choose it will require a certain level of system development on your behalf. The process requires dedication, time and a significant level of programming and DNS experience. Once you have been provisionally accredited you will have access to the 'Registrars Only' site which provides toolkit downloads and a large volume of additional information.

Part B - Check List

The second part of AusRegistry's technical accreditation involves testing your system's registration and management tools to see if all functions are available and operational.

AusRegistry will use a check list to ensure your systems are able to perform the following technical requirements:

  1. Submit to Registry
    Confirmation that a domain creation successfully reaches AusRegistry. This will be done by registering a test domain name.
  2. Update Registrant Details / Domain information publicly available
    Confirmation that domain and contact details can be updated once a domain creation has been processed. Confirm that updated domain and contact information is correctly reflected in the AusRegistry Database.
  3. Registrant access to domain details
    Confirm a registrant's ability to access information pertaining to their Domain Name, e.g. full contact details, expiry dates, etc.
  4. Transferring
    Confirm that your domain transfer system is fully functional
  5. Updating DNS / Delegation Tools
    Test delegation tools to determine method and speed
  6. Domain Name Password Recovery Tool
    Test both automatic retrieval and form retrieval
  7. auDA Requirements on Successful Registration
    Confirm that that certificate of registration is sent along with an email containing the domain password.

Completion of the check list could take up to two business days depending on your systems ability to process certain functions, e.g. a transfer.

If we are unable to perform a required function you will be provided with a breakdown of the exact problem and a method for its resolve.

The ability to perform all technical requirements will be necessary in order to be granted full technical accreditation.

Registrars will also be required to pass an auDA online policy test prior to receiving full accreditation. For more information on the auDA policy test, please visit www.auda.org.au.

To receive further information on the AusRegistry Registrar accreditation process, please email antigone.evangelou@ausregistry.com.au.

Part of the AusRegistry Group
© 2001-2008 AusRegistry Pty Ltd.