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:

Domain type.

This field can have one of the following values: CORPORATE. Rules for maintaining domains of the above types are described in section General Information on Domain Registration in .RU Zone.

If the field type is not included in the application, it is assigned the value CORPORATE by default.

[Optional] [Single] [Read-Only] [Open]

Example:

Brief domain description in an arbitrary textual form.

For second tier domain names in .RU zone it is recommended either to follow the geographical principle or to use the name of the organization for which the domain is being registered. In all other cases the field descr should include Applicant's annotation in English for the domain name requested.

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

Example:

Organization 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 specified in field admin-o is the domain administrator who:

IMPORTANT! Information on the organization specified in field admin-o can only be changed (to re-delegate the domain to another organization or person) by an official letter from the organization 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 is registered in RIPN database, this field should specify its unique identifier assigned in the process of registration.

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

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

Example:

Organization responsible for making domain registration and re-registration payments - for its registration must be used ORGANIZATION TEMPLATE

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

If the organization is not registered in RIPN database, the application should include its template. In this case this field should specify the name of the organization in. (the field org in the organization's template)

Procedure for changing the data in field bill-o is described in document titled Changing the payer for a domain.

[Mandatory] [Multiple] [Read-Write] [Hidden]

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:

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:

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

Any comments, notes.

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

Example:

Any comments or notes to be used by 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 -  for its registration must be used MAINTAINER TEMPLATE.

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

Example:

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:

Domain name

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

This field can not contain more than 128 characters.

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

Example:

domain: kroshka.ru

Domain type

For a domain being registered to an individual person, the value of this field can only be CORPORATE. The rules for maintaining these types of domain are described in section "General Information on Domain Registration in .RU Zone".

[Optional] [Single] [Read-Only] [Open]

Example:

type: CORPORATE

Any brief textual description of the domain.

It is recommended that the first, second or last name of the person to whom the domain is registered (indicated in field "admin-o") be used in personal second tier domain names in .RU zone. In all other cases, Applicant is required to include the field "descr" with an annotation for the requested domain name in English.

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

Example:

descr: kroshka is nickname
descr: of Sidor S Sidorov

The person to whom the domain is being registered and to whom RIPN delegates the domain administration right - for its registration must be used PERSON TEMPLATE.

The person specified in admin-o is the domain administrator. This person:

- establishes the procedure for using the domain;
- selects the organization responsible for maintaining the domain;
- selects the organization responsible for making domain registration and re-registration payments (bill-o).

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

The Procedure of re-delegating CORPORATE type domains is described in Procedure of re-delegating CORPORATE type domains

If a person is registered in RIPN database, this field should contain the unique identifier assigned to this person in the process of registration.

If the person is not registered in RIPN database, it is required that the application include the registration template for this person (#[PERSON TEMPLATE]#). In this case, the field admin-o should contain the name of the person (the field person in the persons template).

It is required that a template submitted for a person contain fields person-r, p-addr, passport, birth-date. It is not allowed to use unique person identifiers from InterNIC or RIPE databases in this field.

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

Example:

admin-o: Sidor S Sidorov

Organization responsible for making domain registration and re-registration payments - for its registration must be used ORGANIZATION TEMPLATE

IMPORTANT! Only a legal entity can be specified in this field.

If an organization is registered in RIPN database, its unique identifier assigned in the process of registration should be specified in this field.

If the organization is not registered in RIPN database then it is required that the application include the template for this organization. In this case, the field should contain the name of the organization (the field "org" in the organization's template)

Procedure for changing the data in the field "bill-o" is described in the document titled "Changing payer for the domain."

[Mandatory] [Multiple] [Read-Write] [Hidden]

Example:

bill-o: DC44-ORG-RIPN

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

Server information should include server name and, if the name of the domain being delegated is included in server name, also the server IP-address or the list of server IP addresses, separated by commas, as well.

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

At least two of the servers listed should be located in different IP nets (in different C class networks in traditional terms) and should have a reliable Internet connection. For the purposes of this document, a "reliable Internet connection" means that the total time of server connection failure 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 zone content of the domain being delegated is that NS records for this domain 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 zone 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 zone, these names are replaced by canonical names, causing error messages. For example:

The zone has the following records:

vasya.ru. NS ns.vasya.ru.
vasya.vasya.ru. A 1.1.1.1

ns.vasya.ru. CNAME vasya.vasya.ru.

The application includes the following records:

domain: vasya.ru
nserver: ns.vasya.ru 1.1.1.1

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 of the zone's NS records.

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

Example 1:

nserver: ns.newtime.ru 193.123.45.67
nserver: ns.provider.ru

Example 2:

nserver: ns.newtime.ru 193.123.45.67
nserver: ns2.newtime.ru 193.123.45.68

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

Example 3:

nserver: ns.newtime.ru 193.123.45.67
nserver: ns3.newtime.ru

-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.

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

Any comments or notes.

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

Example:

remark: created by autodbm@provider.ru

Any comments or notes to be used by 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 - for its registration must be used MAINTAINER TEMPLATE.

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

Example:

mnt-by: NTIME1-MNT-RIPN

The field used for technical support change.

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

Example:

mnt-by: NET1-MNT-RIPN

Information source.

For documents stored in RIPN database, the value of this field should always be "RIPN"

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

Example:

source: RIPN

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: