3.4. Nssets

A nsset contains information which represents a set of name servers.

Namespace: http://www.nic.cz/xml/epp/nsset-1.2
Schema: nsset-1.2.2.xsd


Name-server host mapping is partially based on the standard RFC 5732 but implemented with the following modifications:

  • host names are grouped in a set that is identified by a handle,

  • addition of the report level,

  • association with technical contacts.

3.4.1. Object attributes

In addition to the common attributes, nssets also have the following attributes:


The nsset handle. See Handles of contacts, nssets and keysets.


The 2–10 name servers, consisting of:


Name-server hostname. See Domain names and hostnames.


Name-server IP address(es). (Glue record.)

At least one IP address must be present if and only if the hostname is in the generated zone.

Both IPv4 and IPv6 are allowed, accepted in textual representation:

  • The syntax of an IPv4 address: Four decimal integers 0–255 separated by periods, leading zeroes are optional.

  • The syntax of an IPv6 address is described in RFC 4291#section-2.2.

An IP address must not belong to an invalid range. See the Prohibited networks section in IANA’s Technical requirements for authoritative name servers.


The handle(s) of 1–10 technical contact(s).


The highest level of technical tests to be performed and reported. A higher number means more detail, zero means no tests.

3.4.2. Object states

A nsset can have one or more of the following statuses:

  • ok – no other states are set

  • linked – the nsset has relation to other records in the Registry

  • serverDeleteProhibited – deletion of the nsset is forbidden

  • serverTransferProhibited – transfer of the nsset is forbidden

  • serverUpdateProhibited – update of the nsset is forbidden

  • deleteCandidate – the nsset is scheduled for deletion

3.4.3. Command-response mapping

For command-response mapping see a specific command syntax description: