| TOC |
|
This document specifies the query and response characteristics of the NZ SRS whois service, version 4.00.
1.
Change History
2.
Whois Protocol
2.1.
Internationalized Domain Names (IDNs)
3.
Query Format
4.
Response Format
5.
Specific Field Details
5.1.
Initial fields
5.1.1.
version:
5.1.2.
query_datetime:
5.1.3.
domain_name_idn:
5.1.4.
domain_name_language:
5.1.5.
domain_name_hex:
5.1.6.
domain_name:
5.1.7.
query_status:
5.1.8.
domain_dateregistered:
5.1.9.
domain_datebilleduntil:
5.1.10.
domain_datelastmodified:
5.1.11.
domain_datecancelled:
5.1.12.
domain_datelocked:
5.1.13.
domain_delegaterequested:
5.2.
Contact Fields
5.2.1.
*_name:
5.2.2.
*_address1:
5.2.3.
*_address2:
5.2.4.
*_city:
5.2.5.
*_province:
5.2.6.
*_postalcode:
5.2.7.
*_country:
5.2.8.
*_phone:
5.2.9.
*_fax:
5.2.10.
*_email:
5.3.
Nameserver fields
6.
Examples
6.1.
Query for a domain name which exists
6.2.
Query for an IDN domain name which exists
6.3.
Query for a domain that is not registered
6.4.
Query for a malformed domain name (test+domain.co.nz)
6.5.
Query for a domain name under the wrong apex (example.com)
7.
Acknowledgements
8.
References
§
Authors' Addresses
| TOC |
Original Version
IP (Version 6) address fields added to Nameserver fields
Updated and corrected error codes returned from server
Updated sample output from server
Added details of IDN support
Updated sample output from server
Updated references
| TOC |
The SRS Whois server is based on the protocol described in RFC 3912 (Daigle, L., “WHOIS Protocol Specification,” September 2004.) [refs.RFC3912].
The server listens on TCP port 43 for connections. A client makes a TCP/IP connection to the whois server, and transmits the whois query as a single line, encoded in UTF-8, terminated by a CR LF pair. The format of the query string is described in Section 3 (Query Format).
The whois server then attempts to locate the information requested, and sends a response as a series of UTF-8 encoded lines, each terminated by a CR LF pair. After sending the response the whois server closes the TCP/IP connection. The format of the response is described below.
| TOC |
The SRS Registry and the Whois server support the use of extended character sets in domain names following the recommendations in Internationalizing Domain Names in Applications. (Faltstrom, P., Hoffman, P., and A. Costello, “Internationalizing Domain Names in Applications (IDNA),” March 2003.) [refs.RFC3490] This approach maintains the restriction on DNS names to letters, numbers, full stops (.), and hyphens (-), while potentially supporting a full unicode character set (in practice this will be limited to the characters allowed by the registry).
The SRS Whois server allows queries to be made in the UTF-8 encoding, or in the ASCII encoding. Queries for IDN domains can be made using the Punycode (Zeilenga, K., “Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status,” March 2003.) [refs.RFC3494] ASCII representation, or using a UTF-8 representation.
An example of the whois server's response to an IDN query (Query for an IDN domain name which exists) is provided.
| TOC |
The query consists of a single domain name that is under an apex (that is, the top point of the hierarchy, such as a TLD) managed by the register associated with whois server. (For the New Zealand SRS system this means a domain name ending in "nz".)
No wildcards are permitted; the query string is used literally to match a domain name in the register.
The domain name in the query must be a fully qualified well formed domain name, consisting of letters (see the note below regarding macronised vowels), numbers, full stops (.), and hyphens (-), as described in RFC 1035 (Mockapetris, P., “Domain names - implementation and specification,” November 1987.) [refs.RFC1035]. A trailing full stop (.) indicating an absolute domain name (in BIND syntax) may be present or omitted; if it is present it will be silently discarded, as all domains are assumed to be fully qualified.
The query string must not begin with a hyphen (-) (domain names may not begin with a hyphen anyway, as described in RFC 1035 (Mockapetris, P., “Domain names - implementation and specification,” November 1987.) [refs.RFC1035]). Query strings beginning with a hyphen are reserved for future expansion, to allow passing "command line" flags to the whois server. Currently no flags are defined or permitted.
The domain name in the query may include the Unicode characters for versions of the vowels a, e, i, o, and u with the macron diacritic. These should be encoded in UTF-8. Alternatively, the query may specify the Punycode encoded domain name.
Query strings that do not match the input format will be rejected with a 5xx query_status: response and associated human readable error description, as described below.
| TOC |
The response consists of a series of UTF-8 encoded lines, terminated by CR LF pairs. There are two types of lines in the response format:
Comment lines are identified by an initial percentage symbol (%). The comment lines are intended for human consumption and need not be decoded by a program interacting with the whois server. If appropriate they should be displayed to the user initiating the whois query. They will contain, amongst other things, notification of restrictions on the use of information obtained by the whois server.
The following is a list of all possible field-value fields:
version
query_datetime
domain_name_idn
domain_name_language
domain_name_hex
domain_name
query_status
domain_dateregistered
domain_datebilleduntil
domain_datelastmodified
domain_datecancelled
domain_datelocked
domain_delegaterequested
registrar_name
registrar_address1
registrar_address2
registrar_city
registrar_province
registrar_postalcode
registrar_country
registrar_phone
registrar_fax
registrar_email
registrant_contact_name
registrant_contact_address1
registrant_contact_address2
registrant_contact_city
registrant_contact_province
registrant_contact_postalcode
registrant_contact_country
registrant_contact_phone
registrant_contact_fax
registrant_contact_email
admin_contact_name
admin_contact_address1
admin_contact_address2
admin_contact_city
admin_contact_province
admin_contact_postalcode
admin_contact_country
admin_contact_phone
admin_contact_fax
admin_contact_email
technical_contact_name
technical_contact_address1
technical_contact_address2
technical_contact_city
technical_contact_province
technical_contact_postalcode
technical_contact_country
technical_contact_phone
technical_contact_fax
technical_contact_email
Each of those fields may appear one or may be absent, and if it appears will appear in the order listed above. The fields version:, query_datetime:, domain_name:, and query_status: will always be present.
In addition there is a set of nameserver fields:
ns_name_01
ns_ip4_01
ns_ip6_01
ns_name_02
ns_ip4_02
ns_ip6_02
ns_name_03
ns_ip4_03
ns_ip6_03
...
ns_name_98
ns_name_99
ns_ip4_99
ns_ip6_99
These fields (which hold nameserver details for a domain delegation) will appear for each nameserver recorded in the register for delegation of that domain. For instance if there are three nameservers listed in the register for a domain then these fields will be possible fields:
ns_name_01
ns_ip4_01
ns_ip6_01
ns_name_02
ns_ip4_02
ns_ip6_02
ns_name_03
ns_ip4_03
ns_ip6_03
Any ns_name_NN/ns_ip4_NN/ns_ip6_NN fields will appear after the other fields listed above. The nameservers will appear in the order they were listed by the registrar on creating or updating the domain in the register.
(01 to 99 is considered more than sufficient range for the foreseeable future; only a maximum of 13 nameservers will fit in the current DNS responses, and then only with particular choices of nameserver names, hence a figure nearly an order of magnitude higher is expected to be more than sufficient.)
The fields version:, query_datetime:, domain_name:, and query_status: will always be present. All other fields are subject to empty-field removal. If there is no value in the register for the field, then the field will not be included in the output. This includes the ns_name_NN/ns_ip4_NN/ns_ip6_NN fields. If there is only a name recorded in the register for a particular nameserver, then the ns_name_NN field will be present, but the ns_ip4_NN/ns_ip6_NN fields of the same number will not be present.
The SRS Detailed Requirements Specification (Catalyst IT Ltd, “SRS Detailed Requirements Specification,” August 2002.) [refs.DetailedRequirements] describes the fields which are expected to be present in the register, and hence are expected to be present in a successful whois query for a domain which is in the register. Due to data conversion from the previous register application some fields may not appear on some imported domains (as shown in Section 6.1 (Query for a domain name which exists)). Robust client applications should handle this situation gracefully.
There is no provision for fields to be wrapped onto a second line; all data associated with a given field will be on the same line. The maximum likely length of a field varies from field to field, but no fields will be longer than 1024 characters (and all are expected to be considerably shorter in practice). (Most fields are held in the register in "text" data types, which expand as required, so it is not practical to place a firmer data length restriction on the fields).
The fields may be separated by comments, for example, into groups to make them more human readable, but these comments have no effect on the meaning of the fields.
The formatting and possible values of specific fields are discussed further below.
| TOC |
| TOC |
| TOC |
The version field contains the version number of the output format of the whois server, consisting of a major and a minor part, separated by a full stop (.). The major number will be incremented when the format has changed in a manner that is not compatible with a program parsing the older format (for example, the addition of new fields, or new formatting for existing fields). The minor number will be incremented for any other change.
When the SRS system first went live the version field was:
version: 0.9
| TOC |
The date and time that the query was performed, in local time at the location of the whois server. The date and time will be formatted according to RFC 3339 (Klyne, G. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.) [refs.RFC3339].
| TOC |
If the domain has an IDN, this field will contain the domain name in the script intended by the registrant, encoded in UTF-8.
| TOC |
If the domain has an IDN, this field will contain a string describing the language and script. In the NZ SRS Whois service, the value of this field will be ".NZ LATIN". The Unicode characters accepted by the NZ registry are the macronised versions of the vowels a, e, i, o, and u; as used in the written Māori language.
| TOC |
If the domain has an IDN, this field will contain the domain name with non-ASCII characters encoded in a unicode hex format (for example, m<U+0101>cron.co.nz).
| TOC |
The domain name as stored in the register. Generally this will be the same as the domain name which was queried (from the query string). In the case of queries for domain names containing non-ASCII characters, it will be the encoded domain name stored in the register, formatted according to RFC 3492 (Costello, A., “Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA),” March 2003.) [refs.RFC3492].
| TOC |
The availability status of the domain name which was queried, or a code indicating the error that occurred. The field contains a three digit number followed by a space followed by a human readable string explaining the status number (that string may include spaces, and is considered to +run from the space after the three digit number to the end of line). In the case of successful queries, these human readable strings will correspond to the strings used by the SRS XML protocol to indicate domain status.
There are three groups of status codes:
These groupings are chosen to be overall consistent with RFC 2832 (Hollenbeck, S. and M. Srivastava, “NSI Registry Registrar Protocol (RRP) Version 1.1.0,” May 2000.) [refs.RFC2832], as it is felt potential registrars (and users of the whois interface) are most likely to be familiar with other registry interfaces and their error codes.
The allocated successful query status codes are:
Indicating that the domain is active in the register, is no longer active but is in the period prior to being released for general registrations, or that it is not currently registered and hence available for registration.
The allocated server error status codes are:
All errors in this category are temporary in nature, and the requests should be retried at a later stage. Timeouts may be caused by load on the systems, and so it is appropriate to retry, once, after a short delay. The other statuses may require longer to resolve, and it would be appropriate to present the error to the user, and allow them to retry at a later stage.
The allocated client error status codes are:
All errors in this category are permanent. The request should not be retried as is. Instead the request should be reviewed to ensure that it is well formed, and appropriate for the whois server.
| TOC |
For a domain which is listed in this register, the date and time on which it was entered into the register. The date and time will be formatted according to RFC 3339 (Klyne, G. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.) [refs.RFC3339].
| TOC |
For a domain which is listed in this register, the date and time on which the current payment for the domain registration ends. The date and time will be formatted according to RFC 3339 (Klyne, G. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.) [refs.RFC3339].
| TOC |
For a domain which is listed in this register, the date and time on which the registration was last modified. The date and time will be formatted according to RFC 3339 (Klyne, G. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.) [refs.RFC3339]. This field may be omitted if no modifications have been made since the domain was first registered.
| TOC |
For a domain which was listed in this register but has been cancelled, the date and time on which it was cancelled. The date and time will be formatted according to RFC 3339 (Klyne, G. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.) [refs.RFC3339].
| TOC |
For a domain which is listed in the register but has been locked (for example, by the registry while a dispute is resolved), the date and time on which the domain was locked. The date and time will be formatted according to RFC 3339 (Klyne, G. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.) [refs.RFC3339].
| TOC |
For a domain which is listed in the register, "yes" or "no", depending on whether the domain is marked for export into the DNS zone as a delegation. If the domain_delegaterequested: is "no", then the domain will not appear in the DNS even if all other information (for example, suitable nameservers) is present to otherwise allow it to do so. If set to "yes", then the domain will appear in the DNS providing the other criteria are satisfied.
| TOC |
There are four sets of contact fields (registrar_*, registrant_contact_*, admin_contact_*, technical_contact_*) each of which contains the same field information (name, address1, address2, city, province, postalcode, country, phone, fax, email). These fields will report the contact information held in the register for the registrar, registrant, admin contact and technical contact as appropriate.
As with all other fields, fields for which there is no data in the register will be omitted.
The format of individual fields is as follows.
| TOC |
Free format name of the registrar, registrant, or admin/technical contact person, as held in the register.
| TOC |
Free format first line of the postal or physical address of the registrar, registrant, or admin/technical contact, as held in the register.
| TOC |
Free format second line of the postal or physical address of the registrar, registrant, or admin/technical contact, as held in the register. This field will be omitted if the postal or physical address is listed entirely in the address1 field in the register.
| TOC |
Free format name of city or other locality for the postal or physical address of the registrar, registrant, or admin/technical contact, as held in the register.
| TOC |
Free format name of the province or region or state for the postal or physical address of the registrar, registrant, or admin/technical contact, as held in the register. This field will be omitted if the postal or physical address held in the register does not list a province/region/state.
| TOC |
Free format postal code for the postal or physical address of the registrar, registrant, or admin/technical contact, as held in the register. This field will be omitted if the postal or physical address held in the register does not include a postal code.
| TOC |
Two letter country code of the postal or physical address of the registrar, registrant, or admin/technical contact, followed by the accepted expansion of that country code in parenthesis, as held in the register. For instance:
registrar_country: NZ (New Zealand)
The applicable country codes are taken from two letter country codes in ISO 3166 (International Organization for Standardization, “Codes for the representation of names of countries, 3rd edition,” August 1988.) [refs.ISO3166].
| TOC |
Contact phone number for the registrar, registrant, or admin/technical contact, as held in the register. The phone number is formatted with a leading plus sign (+), followed by the country code, followed by a space, followed (if held in the register) by an area code, followed by a space, followed by a free format E.164 style phone number.
For example, the following are all (individually) valid examples:
registrar_phone: +64 4 555 5555
registrar_phone: +64 4 555-5555
registrar_phone: +65 555-5555
In the third example there are two spaces (one either side of the non-existent area code) in the output.
| TOC |
Contact fax number for the registrar, registrant, or admin/technical contact, as held in the register. The number is formatted as for the *_phone fields (described above).
| TOC |
Contact email address for the registrar, registrant,or admin/technical contact, as held in the register. The email address is formatted as a RFC 5321 (Klensin, J., “Simple Mail Transfer Protocol,” October 2008.) [refs.RFC5321] email address, omitting the opening angle bracket (<) and closing angle bracket (>).
For example:
registrar_email: contact@registrar.example.com
| TOC |
Each delegated domain has two or more nameservers associated with it; however domains may exist in the register with fewer than two nameservers, in which case they will not be present in the DNS (domains may also not be present in the DNS if the domain_delegaterequested: field is "no").
The nameservers are listed sequentially in the order that they are held in the register (and hence the order they were received from the registrar), as _01, _02, and so on. There will not be any gaps in the sequence.
For each nameserver, the ns_name_NN field will list the domain name of the nameserver held in the register, the ns_ip4_NN field will list the IP (version 4) address of the name server held in the register (if any), and the ns_ip6_NN field will list the IP (version 6) address of the name server held in the register (if any).
If no IP (version 4) address is held in the register for a particular nameserver for that domain, then the ns_ip4_NN field will be omitted. If no IP (version 6) address is held in the register for a particular nameserver for that domain, then the ns_ip6_NN field will be omitted.
ns_ip4_NN/ns_ip6_NN fields (with IP addresses) may appear for out-of-zone delegations if these details are held in the register (i.e., were sent by the registrar when creating or updating the registration), and may be absent even for in-zone delegations if the details have not been supplied by the registrar. The whois server reflects what is actually held in the register, even if that is not complete, or contains details that are not required for the DNS delegation. If the details in the register are not complete enough for a DNS delegation, then the domain will not be delegated in the DNS.
The IP (version 4) addresses in the ns_ip4_NN fields will be formatted as a dotted quad (for example, NN.NN.NN.NN), without zero padding on any segment. Any well-formed IP (version 4) address may appear: there is no filtering of martians (for example, RFC 1918 (Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and E. Lear, “Address Allocation for Private Internets,” February 1996.) [refs.RFC1918] addresses) performed in the SRS or the whois server -- instead registrars are expected to supply sensible data, but whatever is held in the register will be returned in the whois query.
The IP (version 6) addresses in the ns_ip6_NN will be formatted in the same format as it was received by the register. Any well formed IP (version 6) may appear.
| TOC |
| TOC |
% New Zealand Domain Name Registry Limited % Users confirm on submission their agreement to all published Terms % version: 4.00 query_datetime: 2009-12-03T09:05:27+13:00 domain_name: dnc.org.nz query_status: 200 Active domain_dateregistered: 2002-04-23T00:00:00+12:00 domain_datebilleduntil: 2009-12-23T00:00:00+13:00 domain_datelastmodified: 2009-11-23T23:41:30+13:00 domain_delegaterequested: yes % registrar_name: Domain Name Commissioner registrar_address1: PO Box 11881 registrar_city: Wellington registrar_country: NZ (New Zealand) registrar_phone: +64 4 472-1600 registrar_fax: +64 4 495-2115 registrar_email: info@dnc.org.nz % registrant_contact_name: Internet New Zealand Incorporated registrant_contact_address1: PO Box 11-881 registrant_contact_city: Wellington registrant_contact_postalcode: 6001 registrant_contact_country: NZ (New Zealand) registrant_contact_phone: +64 4 472 1600 registrant_contact_fax: +64 4 495 2115 registrant_contact_email: exe.dir@internetnz.net.nz % admin_contact_name: Executive Director admin_contact_address1: InternetNZ admin_contact_address2: PO Box 11-881 admin_contact_city: Wellington admin_contact_postalcode: 6001 admin_contact_country: NZ (New Zealand) admin_contact_phone: +64 4 472 1600 admin_contact_fax: +64 4 495 2115 admin_contact_email: exe.dir@internetnz.net.nz % technical_contact_name: Technical Manager technical_contact_address1: InternetNZ technical_contact_address2: PO Box 11-881 technical_contact_address2: Wellington technical_contact_postalcode: 6001 technical_contact_country: NZ (NEW ZEALAND) technical_contact_phone: +64 4 472 1600 technical_contact_fax: +64 4 495 2115 technical_contact_email: soa@internetnz.net.nz % ns_name_01: ns1.internetnz.net.nz ns_name_02: ns3.catalyst.net.nz ns_name_03: ns1.serion.co.nz % % Users are advised that the following activities are strictly forbidden. % % Using multiple WHOIS queries, or using the output of multiple WHOIS % queries in conjunction with any other facility or service, to enable % or effect a download of part or all of the .nz Register. % % Using any information contained in the WHOIS query output to attempt a % targeted contact campaign with any person, or any organisation, using any % medium. % % A breach of these conditions will be treated as a breach of the .nz Policies % and Procedures. Sanctions in line with those specified in the policies and % procedures at www.dnc.org.nz may result from any breach. % % Copyright InternetNZ
| TOC |
% New Zealand Domain Name Registry Limited % Users confirm on submission their agreement to all published Terms % version: 4.00 query_datetime: 2009-12-03T13:30:33+13:00 domain_name_idn: mācron.co.nz domain_name_language: .NZ LATIN domain_name_hex: m<U+0101>cron.co.nz domain_name: xn--mcron-fwa.co.nz query_status: 200 Active domain_dateregistered: 2009-10-30T17:05:24+13:00 domain_datebilleduntil: 2010-01-30T17:05:24+13:00 domain_datelastmodified: 2009-10-30T17:05:24+13:00 domain_delegaterequested: yes % registrar_name: Domain Name Commissioner registrar_address1: PO Box 11881 registrar_city: Wellington registrar_country: NZ (New Zealand) registrar_phone: +64 4 472-1600 registrar_fax: +64 4 495-2115 registrar_email: info@dnc.org.nz % registrant_contact_name: Internet New Zealand Incorporated registrant_contact_address1: PO Box 11-881 registrant_contact_city: Wellington registrant_contact_postalcode: 6001 registrant_contact_country: NZ (New Zealand) registrant_contact_phone: +64 4 472 1600 registrant_contact_fax: +64 4 495 2115 registrant_contact_email: exe.dir@internetnz.net.nz % admin_contact_name: Executive Director admin_contact_address1: InternetNZ admin_contact_address2: PO Box 11-881 admin_contact_city: Wellington admin_contact_postalcode: 6001 admin_contact_country: NZ (New Zealand) admin_contact_phone: +64 4 472 1600 admin_contact_fax: +64 4 495 2115 admin_contact_email: exe.dir@internetnz.net.nz % technical_contact_name: Technical Manager technical_contact_address1: InternetNZ technical_contact_address2: PO Box 11-881 technical_contact_address2: Wellington technical_contact_postalcode: 6001 technical_contact_country: NZ (NEW ZEALAND) technical_contact_phone: +64 4 472 1600 technical_contact_fax: +64 4 495 2115 technical_contact_email: soa@internetnz.net.nz % ns_name_01: ns1.internetnz.net.nz ns_name_02: ns3.catalyst.net.nz ns_name_03: ns1.serion.co.nz % % Users are advised that the following activities are strictly % forbidden. % % Using multiple WHOIS queries, or using the output of multiple WHOIS % queries in conjunction with any other facility or service, to enable % or effect a download of part or all of the .nz Register. % % Using any information contained in the WHOIS query output to attempt a % targeted contact campaign with any person, or any organisation, using % any medium. % % A breach of these conditions will be treated as a breach of the .nz Policies % and Procedures. Sanctions in line with those specified in the policies and % procedures at www.dnc.org.nz may result from any breach. % % Copyright InternetNZ
| TOC |
% New Zealand Domain Name Registry Limited % Users confirm on submission their agreement to all published Terms % version: 4.00 query_datetime: 2002-09-05T14:47:37+12:00 domain_name: notregistered.org.nz query_status: 220 Available % % % % % % % Users are advised that the following activities are strictly forbidden. % % Using multiple WHOIS queries, or using the output of multiple WHOIS % queries in conjunction with any other facility or service, to enable % or effect a download of part or all of the .nz Register. % % Using any information contained in the WHOIS query output to attempt a % targeted contact campaign with any person, or any organisation, using any % medium. % % A breach of these conditions will be treated as a breach of the .nz Policies % and Procedures. Sanctions in line with those specified in the policies and % procedures at www.dnc.org.nz may result from any breach. % % Copyright InternetNZ
| TOC |
% New Zealand Domain Name Registry Limited % Users confirm on submission their agreement to all published Terms % version: 4.00 domain_name: test+domain.co.nz query_status: 500 Invalid characters in query string query_datetime: 2002-09-05T14:47:37+12:00 % % % % % % % Users are advised that the following activities are strictly forbidden. % % Using multiple WHOIS queries, or using the output of multiple WHOIS % queries in conjunction with any other facility or service, to enable % or effect a download of part or all of the .nz Register. % % Using any information contained in the WHOIS query output to attempt a % targeted contact campaign with any person, or any organisation, using any % medium. % % A breach of these conditions will be treated as a breach of the .nz Policies % and Procedures. Sanctions in line with those specified in the policies and % procedures at www.dnc.org.nz may result from any breach. % % Copyright InternetNZ
| TOC |
% New Zealand Domain Name Registry Limited % Users confirm on submission their agreement to all published Terms % version: 4.00 domain_name: example.com query_status: 510 Domain is not managed by this register query_datetime: 2002-09-05T14:47:37+12:00 % % % % % % % Users are advised that the following activities are strictly forbidden. % % Using multiple WHOIS queries, or using the output of multiple WHOIS % queries in conjunction with any other facility or service, to enable % or effect a download of part or all of the .nz Register. % % Using any information contained in the WHOIS query output to attempt a % targeted contact campaign with any person, or any organisation, using any % medium. % % A breach of these conditions will be treated as a breach of the .nz Policies % and Procedures. Sanctions in line with those specified in the policies and % procedures at www.dnc.org.nz may result from any breach. % % Copyright InternetNZ
| TOC |
The author would like to thank the following groups and individuals for reviewing this specification in draft format and providing very helpful comments.
| TOC |
| TOC |
| Ewen McNeill | |
| New Zealand Domain Name Registry Ltd, trading as .nz Registry Services. | |
| PO Box 24361 | |
| Wellington | |
| New Zealand | |
| Email: | support@nzrs.net.nz |
| URI: | http://www.nzrs.net.nz/ |
| Evan Giles | |
| New Zealand Domain Name Registry Ltd, trading as .nz Registry Services. | |
| PO Box 24361 | |
| Wellington | |
| New Zealand | |
| Email: | support@nzrs.net.nz |
| URI: | http://www.nzrs.net.nz/ |
| Andrew Ruthven | |
| New Zealand Domain Name Registry Ltd, trading as .nz Registry Services. | |
| PO Box 24361 | |
| Wellington | |
| New Zealand | |
| Email: | support@nzrs.net.nz |
| URI: | http://www.nzrs.net.nz/ |