News
DNRS release 4.00
Posted on 2010-03-18
Version 4.00 of the DNRS has been released.
Changes to the protocol have been made. The DNRS is now capable of IDN handling. Some transactions had to be changed to allow IDN registration and management.
It also allows general tidy ups and fixes a few bugs.
You find the packages on our Download page
DNRS release 3.00
Posted on 2009-06-04
Version 3.00 of the DNRS has been released.
Changes to the protocol have been made. Some transactions have been renamed to follow the overall nameing scheme and also the hard coded values of the VerMajor field have been removed.
It also allows general tidy ups and fixes a few bugs.
You find the packages on our Download page
DNRS release 2.07
Posted on 2008-11-17
A new public release of the DNRS.
This release allows some improvements to the UpgradeManager, replication improvements, Changes to allow table partitioning, bug fixes and just a few other general tidy ups. See the change log for more details.
NZ-SRS (& DNRS) Documentation Update
Posted on 2008-05-21
A project to review and rewrite the documentation or the NZ-SRS is currently underway. In addition to improving upon the existing NZ-SRS documentation, one of the aims of the project is to promote the NZ-SRS as an alternative standards-based protocol to the Extensible Provisioning Protocol (EPP).
The project has been split into two phases:
Phase one involves producing an NZ-SRS Standards document that documents the NZ-SRS as a standard and submitting it to the IETF internet drafts process with the ultimate aim of achieving an RFC publication status. This document excludes any .nz implementation specific details as these details are covered in phase two.
Phase two involves producing an NZ-SRS Implementation document that takes the NZ-SRS Standard and details all the .nz business rules that have been used to implement the NZ-SRS for the .nz name space. For example the NZ-SRS Standard document will describe the type of grace periods used and the NZ-SRS Implementation document will specify the specific values used for the grace periods.
NZRS are pleased to announce that phase one has been completed and the internet draft of the NZ-SRS standard has been submitted to the internet drafts process.
I would like to thank the author Matthew Hunt, and the NZ-SRS support team at NZRS and Catalyst IT Limited for their help in producing this document.
The draft document is available on the NZRS website in txt, or pdf format:
http://www.nzrs.net.nz/downloads/draft-nzrs-srs-00-fo.pdf
http://www.nzrs.net.nz/downloads/draft-nzrs-srs-00.pdf
http://www.nzrs.net.nz/downloads/draft-nzrs-srs-00.txt
Alternatively it can be found in the IETF drafts:
http://www.ietf.org/internet-drafts/draft-nzrs-srs-00.txt
If you have any comments or suggestions on the standards document, then these can be made via the mailing list (see below) or alternatively sent to support <at> nzrs.net.nz
Details of the IETF submission:
A new version of I-D, draft-nzrs-srs-00.txt has been successfully submitted by Matthew Hunt and posted to the IETF repository.
Filename: draft-nzrs-srs
Revision: 00
Title: System for Managing a Shared Domain Registry
Creation_date: 2008-05-18
WG ID: Independent Submission
Number_of_pages: 120
Abstract:
This document describes the typical usage and communication protocol of a client/server shared registry system for management of domain name registrations. The system described is a "thick registry" system, providing support for the storage and management of both the technical and the registrant contact information concerning domain registrations. The system relies on the existing HTTP and HTTPS infrastructure for transport and secure transfer to avoid having to implement a dedicated protocol and server environment. A bespoke XML format is used to communicate between clients and the SRS server.
Comments are solicited and should be addressed to the mailing list at srsstandards-l <at>nzrs.net.nz and/or the author. The mailing list management page can be found at <https://mailman.nzrs.net.nz/cgi-bin/mailman/listinfo/srsstandards-l>.