.co.nz – Openprovider

This article describes the procedures and requirements of .co.nz domain names.
Click on the subject below to open the dropdown for more information.

Registration

Successful domain registration via RCP or API requires:

two or more nameservers or a nameserver group

If you are registering a .nz (top level) domain and the same domain name already exists in one of the second level domains (like .co.nz), it is mandatory to use the UDAI (authcode) of that domain to register the .NZ domain name. If you have any issues getting your UDAI, you can email at info@dnc.org.nz.

New WHOIS Privacy Setting for .NZ domains from March 8, 2023.

Whether contact information is displayed in the WHOIS now depends on the domain's new PRIVACY attribute. The value is default set to PRIVATE for individuals (personal data will not be displayed) and PUBLIC for organisations.

Individual Registrant Privacy Option is no longer available.

Transfer

Successful domain transfer via RCP or API requires:

authorisation code (known as UDAI)
two or more nameservers or a nameserver group
registrant e-mail address verification applies

The UDAI changes automatically upon certain domain operations (e.g. update and transfer). The UDAI will expire after 30 days. Code check can be done here: https://old.dnc.org.nz/udai

Authorization code required	yes
Method of confirmation	authcode
Registration period after transfer	unchanged
Average transfer time	Realtime
Advanced and simple transfers available	Contact our Sales department to check if easy transfer of 100 or more .co.nz domains is available.

Outgoing transfer

The UDAI (Authorization Code) needs to be manually requested by Openprovider Support.
Please send an email to support@openprovider.com with the subject
"UDAI Request for the domain <domainname.nz>"

Update

Owner change (trade)

requested as a normal domain update via RCP or API
processed realtime

Other update

requested via RCP or API
processed realtime

Deletion / Restore

Delete

requested via RCP or API
processed realtime
will result in a quarantine period

Restore / reactivate

Quarantine period of 90 days (or Pending Release Period)
At any time before the Pending Release Period has ended:

a. the Registrar can reinstate the Cancelled Domain Name for the Domain Name Holder.

b. the Domain Name Holder can transfer the Cancelled Domain Name to a new Registrar and request that Registrar to reinstate it for them.

Detailed extension information

Registry	Registry: Domain Name Commission NZ Registry whois: whois.srs.net.nz Registry web based whois: https://dnc.org.nz/whois/whois-lookup/ Registry zonefile updates:
Domain lifecycle	domain lifecycle
Technical information	DNSSEC support: yes Min: 3 Max: 63 Alphanumeric and a hyphen except in the first or last position IDN: Yes Registration period: 1-10 years Renewal date offset: 0 days The number of days before the registry's expiration date, that Openprovider requires the domain to be renewed or expired. More info. Note that the dates as shown in your Openprovider account are always leading, even if they do not match the renewal date offset mentioned here. Soft quarantine period: 42 days During this period, following after an expiration, the domain can be restored for free. This period does not apply if the domain is deleted explicitly. More info. Quarantine period: 90 days During this period, an expired or deleted domain name can be reactivated at an additional fee.
Restrictions	Local presence required? no Does Openprovider provide local presence services? no Local activity required? no Correct nameserver configuration required? no The Domain(s) can be registered without further limitations.
Policies	Policies: https://dnc.org.nz/about/compliance-and-enforcement/nz-policies/ Rules for Uniform Domain Name Dispute Resolution Policy: http://www.icann.org/en/help/dndr/udrp/rules
Registration agreement	The registry requires that a registration agreement is in place between the provider and the domain holder. The text of this registration agreement and any required supplements is the following: General registration agreement

Due to the regular changes in registry rules and configuration or missing information from registry side, and despite our effort to keep our knowledge base up-to-date, information in the knowledge base may be outdated or incorrect. If you encounter some issue, please report it through the "HotJar" feedback collector on the bottom right, or (if it is blocked by your browser) by clicking the "Submit a request" link below. No rights can be derived from the information in this knowledge base. If there is discrepancy between the knowledge base and the process in Openprovider, the process in Openprovider is leading.