Domain name

Domain name should consist of more than one character, begin and end with a Roman letter or with a digit. Letters, digits or the hyphen character can be used in the middle of a domain name. A domain name can not consist of digits only.

A field can contain not more than 128 characters.

[Mandatory] [Single] [Read-Only] [Open]

Example:

Brief domain description in an arbitrary textual form (it is available information).

[Optional] [Multiple] [Read-Write] [Open]

Example:

Extended domain description in an arbitrary textual form.

For third level of domain names in .COM.RU, .NET.RU, .ORG.RU and .PP.RU zones it is recommended to use the name of the organization or person for which the domain is being registered. In all other cases the field comp-d should include Applicant's annotation for the domain name requested (a detailed description of the project, for which the domain is registerred).

[Optional] [Multiple] [Read-Only] [Open]

Organization or person to which the domain is being registered and to which RIPN delegates domain administration rights - for its registration must be used ORGANIZATION TEMPLATE

The organization or person specified in field admin-o is the domain administrator who:

IMPORTANT! Information on the organization or person specified in field admin-o can only be changed (to re-delegate the domain to another organization or to another person) by an official letter from the organization or the person specified in field admin-o.

The procedure for re-delegating CORPORATE type domains is described in section Procedures for Re-delegating CORPORATE Type Domains .

If an organization or person are registered in RIPN database, this field should specify its unique identifier assigned in the process of registration.

If an organization or person are not registered in RIPN database, the application should include its registration template. In this case this field should specify the names of the organization or person (the field org in the organization's template or the field person in the person template).

[Mandatory] [Multiple] [Read-Only] [Open]

Example:

The field contains information on domain name servers (DNS) supporting the domain being delegated.

Server information includes server name and, if server name contains the name of domain being delegated, it also includes the IP-address of the server or the list of server IP addresses, separated by commas.

The order in which servers are listed does not matter, as they are entered in the database in the alphabetical order.

At least two of the servers listed should be located in different IP nets (in different C class nets in traditional terms) and have a reliable Internet connection. For the purposes of this document, a reliable Internet connection means that the total time of no connection with the server does not exceed 2 hours per day.

Server name should contain not more than 128 characters, server IP address list should contain not more than 160 characters.

An imperative requirement when checking the area content of the domain being delegated is that this domain's NS records located on primary and secondary servers should be identical.

In cases when objects related to the domain being delegated include E-mail addresses containing the name of that domain , the domain area should contain either A or MX records for the domain being delegated, as the object should be accessible via E-mail.

Please note that CNAME records should not be used to define server names. In the process of verifying the operational capability of the area, these names are replaced by canonical names, causing error messages. For example:

The zone has the following records:

The application includes the following records:

In this kind of situation the robot will report an error due to the discrepancy between the server list specified in the application and that specified in the zones NS records.

[Mandatory] [Multiple] [Read-Write] [Open]

Example 1:

Example 2:

- in this case the information in the field is correct, however, since the primary and secondary servers are located in the same C class network, the entire form will be considered to be completed incorrectly, unless the template includes additional nserver type fields.

Example 3:

-in this case the field is completed incorrectly. If server name contains the name of the domain being delegated then the IP address of the server should be specified.

Any comments, notes.

[Optional] [Multiple] [Read-Write] [Open]

Example:

Any comments or notes included for RIPN.

Information in this field should be entered in Russian (for non-russian organization - in English).

[Optional] [Multiple] [Read-Write] [Hidden]

Unique identifier of the maintainer responsible for ensuring that RIPN database contains correct domain information.

[Mandatory] [Single] [Read-Write] [Open]

mnt-by: NTIME1-MNT-RIPN

The field is used only if the technical support in "mnt-by" field must be changed.

[Optional] [Single] [Read-Write] [Open]

Example:

mnt-by: NET1-MNT-RIPN

Information source.

For documents in RIPN database, this field should always have the value RIPN

[Mandatory] [Single] [Read-Only] [Open]

Example: