2.2.1. RU-NIC provides services to persons that have entered into a Service Agreement with RU-NIC. The conclusion of the Agreement is preceded by the registration of the Customer on RU-NIC's database. The Customer is responsible for selecting and registering individual administrative and technical passwords during the registration on RU-NIC's database, for preserving their confidentiality, and for all actions that take place as a result of using the passwords.

2.2.2. All information provided by the Customer at the conclusion of the Agreement must be factual. If the Customer provides false information, the provision of services to the Customer may be terminated.

2.2.3. In the case of any doubt as to the authenticity of the information provided by the Customer, RU-NIC may request substantiation of the information and/or additional information during the entire term of the provision of services. Such requests are sent to the Customer over the standard communication channel.

2.2.4. If the Customer fails to support the previously provided information and/or provide any requested additional information within fourteen (14) calendar days from the day RU-NIC sends the first request, RU-NIC may:

All the above restrictions can be lifted within three (3) working days from the day the Customer submits the requested information.

If the Customer fails to provide any requested information within thirty (30) calendar days from the day RU-NIC sends the first request, the provision of services to the Customer can be terminated.

2.3.1. The ordering of a service indicates the Customer's agreement to pay for the service at the prices current on the day the processing of the Order begins.

2.3.2 Services are ordered on RU-NIC's web site at http://www.nic.ru.

2.3.3. An Order for a service may only be cancelled before its processing begins. The Customer can cancel an Order on RU-NIC's web site at http://www.nic.ru in the "Manage your account" section ("Orders", the "Processing queue, order removal" link).

2.3.4. An Order is considered ready for processing and will be processed if the Customer has entered into a Agreement with RU-NIC and has in their Agreement Account sufficient funds to pay for all ordered services. Any Order that cannot be processed within 3 months will be deleted.

2.3.5. RU-NIC will process any Orders for new services on a first-come basis. The sequence in which new Orders are processed can be changed on RU-NIC's web site at http://www.nic.ru in the "Manage your account" section ("Orders", the "Processing queue, order removal" link).

2.3.6. Orders for the renewal of services whose renewal has not been cancelled by the Customer are processed in the sequence in which their respective terms expire.

2.3.7. Orders for the renewal of services have a higher processing priority than Orders for new services.

2.3.8. If a domain maintenance service is ordered together (on the same Order) with the domain registration service, and the domain name cannot be registered, the domain maintenance service will not be provided.

2.3.9. If one of the services Primary-Standard, Primary-Auto or Secondary is already active for any domain name, such a service for lower-level domain names within that domain name may be ordered only in case the order was received from a Customer, who owns the active service.

2.3.10. If the hosting service is active for any domain name, the services Primary-Standard, Primary-Auto, Secondary for lower-lever domain names within that domain name may be provided only in case the order is received from the Customer, who owns the active hosting service.

2.3.11. RU-NIC has the right to refuse providing any of the services Primary-Standard, Primary-Auto or Secondary to the Customer in case the service is ordered for a domain name of general use (GEOGRAPHICAL or GENERIC type).

2.3.12. Domain maintenance service is provided by RU-NIC to the Customer within 1 (one) year term. Term of validity of the service may be extended for the next year.

2.4.1. The costs of RU-NIC's services are specified in the Service Agreement.

2.4.2. Invoicing:

RU-NIC will generate an invoice after RU-NIC receives the Customer's request for the invoice. Invoices can be requested via RU-NIC's web site at http://www.nic.ru in the "Manage your account" section ("Payment", the "Recharge your account" link). If the Customer has entered into a Agreement with RU-NIC, the original of the invoice is sent to the Customer by post:

The Customer can print a copy of any issued invoice from RU-NIC's web site at http://www.nic.ru in the "Manage your account" section ("Payment", the "Bills issued" link).

2.4.3. When making a payment, the Customer must indicate the number of their Agreement with RU-NIC on the payment documents.

2.4.4. RU-NIC keeps track of the Customer's payments and the services provided to the Customer, based on the current rates for the services, using the Customer's Agreement Account. Any payment made by the Customer is credited to their Agreement Account after the money has been credited to RU-NIC's bank account and RU-NIC has received from the bank a document identifying the payment.

The Customer can access the information of their Agreement Account on RU-NIC's web site at http://www.nic.ru in the "Manage your account" section ("Payment", the "Account balance" link).

2.4.5. On termination of the Agreement RU-NIC will refund the Customer's unused balance by bank transfer to the Customer's bank account at any bank resident in the Russian Federation. RU-NIC will take steps to complete the refund within seven (7) working days from the day the Customer submits a written request for the refund with the full bank details of the recipient.

2.5.1. RU-NIC will renew the provision of a service if the balance of the Customer's Agreement Account is sufficient to cover the cost of the renewal and if the Customer has not cancelled the renewal. At that term of validity of the service is extended for 1 (one) year from the date of service termination set earlier.

The Customer hereby agrees that the funds for renewing other services used by the Customer are blocked in the sequence in which the terms of these services expire (the funds for a service whose term expires earlier are blocked earlier). Should the Customer change order execution sequence, the funds will be blocked on the contract personal account in a manner established by the Customer.

Unless if otherwise specified by the Customer using e-payment systems. In this case the service renewal procedure will be established by the Customer as scheduled by the e-payment systems.

2.5.2. The absence of the Customer's cancellation of a service renewal indicates the Customer's agreement to the renewal and to the Customer's Agreement Account being debited for the renewal. RU-NIC will send the Customer a notice about any forthcoming renewal over the standard communication channel two (2) months prior to the expiry of the service term.

2.5.3. Funds for a service renewal are frozen (reserved) automatically by RU-NIC in the Customer's Agreement Account no earlier than eight (8) calendar days prior to the expiry of the service term, if the Customer has not cancelled the renewal.

The Customer's Agreement Account is debited automatically by RU-NIC for a service renewal no earlier than one (1) calendar day prior to the expiry of the service term, if the Customer has not cancelled the renewal.

2.5.4. On the Customer's initiative money blocking and charging off from his Service Agreement personal account for service renewal can be executed by RU-NIC before the terms specified in the paragraph 2.5.3 of the present Schedule, but not earlier than 2 (two) months before the service expires. In such case money blocking and charging-off is made within 24 hours since the Customer's consent to pay in advance for service renewal is received by RU-NIC. The Customer can confirm his agreement for ahead of schedule service renewal payment on RU-NIC's web-server in the section "Manage your account" ("Services", the link "Services renewal").

2.5.5. The Customer may cancel a service renewal before the renewal service is provided to him. Renewals are cancelled on RU-NIC's web site at http://www.nic.ru in the "Manage your account" section ("Services", the "Renew services" link).

2.5.6. The provision of a service will be suspended if it is not renewed by the Customer before the expiry of the service term. RU-NIC will terminate the provision of a service if the Customer does not renew it within thirty (30) calendar days after the expiry of the service term.

a) The server must be configured as the primary or a secondary DNS server for the Customer's zone according to the DNS standards, and must be connected to the Internet.

b) The server's settings must allow zone transfer of the Customer's zone on requests from the IP address of the DNS server ns4.nic.ru and the IP address of the DNS server ns8.nic.ru.

3.4.1. DNS server ns4.nic.ru will request the specified primary DNS server for zone transfer from the moment the provision of the service begins.

3.4.2. If zone transfer to DNS server ns4.nic.ru is not possible because the requirements defined in section 3.3 are not met, DNS server ns4.nic.ru will periodically repeat its requests for zone transfer for four (4) calendar days.

3.4.3. If during the period specified in section 3.4.2 all requests of DNS server ns4.nic.ru for zone transfer are not successful, DNS server ns4.nic.ru will stop its attempts to perform zone transfer for a period of four (4) calendar days. The Customer can manually activate zone transfer to RU-NIC's DNS server:

3.4.4. DNS server ns8.nic.ru will request a primary DNS server specified by a Customer in the services settings for zone transfer. If it is not possible to transfer a zone file from a primary DNS server specified by a Customer to DNS-server ns8.nic.ru because the requirements defined in section 3.3 are not met, DNS-server ns8.nic.ru will request ns4.nic.ru DNS-server for zone file transfer.

3.5.1. Information about a zone on RU-NIC's DNS servers is updated based on the "Retry", "Refresh" and "Expire" parameters in the zone's SOA record.

3.5.2. If zone transfer to RU-NIC's DNS server is not possible because the requirements defined in section 3.3 are not met, RU-NIC's DNS server will repeat its requests for zone transfer with the "Retry" frequency for the "Expire" period.

3.5.3. If during the "Expire" period all requests of RU-NIC's DNS server for zone transfer are not successful, RU-NIC's DNS server will stop its attempts to perform zone transfer for a period of four (4) calendar days.

The Customer can manually activate zone transfer to RU-NIC's DNS server following the procedure given in section 3.4.3 of this Schedule.

- log into the section "Manage your account";
- select "Review and update data" in the "Services" menu;
- find the service (Secondary service for the domain);
- click on the "modify" link in the "Modify parameters" column;
- make necessary changes;
- save the changes.

- RU-NIC's equipment has been configured as the primary DNS server for the Customer's zone according to the DNS standards; the server's settings must allow zone transfer of the Customer's zone on request from the IP addresses of the servers specified by the Customer in the service settings as secondary DNS servers;
- the Customer has been given the opportunity to manually add records to the zone; the records must be compliant with the DNS standards.

- the e-mail address in the SOA record will be copied from the "mnt-nfy" field of the Agreement or, if this field is empty, from the "e-mail" field of the Agreement;
- if the service is ordered together (on the same Order) with the domain registration service and/or other domain maintenance services (Secondary, Mail-forwarding, Web-forwarding), an NS record with information about the domain's DNS servers and/or records required for the provision of the maintenance services will be automatically added to the zone.

4.4.1. Changes are made by the Customer, using the zone file editor, provided by RU-NIC. The editor can be accessed from RU-NIC's web site at http://www.nic.ru.

Order of changes:

The zone file editor can also be entered on the RU-NIC's web site, at http://www.dns-master.ru.

4.4.2. Zone file editing is performed using the versions support system, so the Customer is able to recover any previously saved version of a zone file.

4.4.3. The Customer can make changes in the zone and change the following types of records:

4.4.4. RU-NIC is not liable for the consequences of any errors made by the Customer when adding records to a zone.

- log into the "Manage your account" section;
- select "Review and update data" in the "Services" menu;
- find the service (Primary-Standard service for the domain);
- click on the "Secondary IP addresses" link in the "Modify parameters" column;
- make necessary changes;
- save the changes.

4.6.1. On switching from the Primary-Standard service to the Primary-Auto service:

4.6.2. Switching from the Primary-Standard service to the Primary-Auto service is done automatically after the Customer has ordered and paid for the Primary-Auto service. The Primary-Standard service will then be suspended, its term will not change, and any money already paid for the service will not be refunded.

4.6.3. The Customer will be able to resume the use of the suspended Primary-Standard service and restore any of the previously saved zone file versions at any time before the service term expires.

To resume the use of the Primary-Standard service:

After switching to the Primary-Standard service the Primary-Auto service will be temporally switched off by RU-NIC, its term does not change, and there is no refund.

- the e-mail address in the SOA record will be RU-NIC's e-mail address support@nic.ru, which cannot be subsequently changed;
- if the service is ordered together (on the same Order) with the domain registration service and/or other domain maintenance services (Secondary, Mail-forwarding, Web-forwarding), an NS record with information about the domain's DNS servers and/or records required for the provision of the maintenance services will be automatically added to the zone

5.4.1. If a domain is not administered under the Customer's Agreement, when the list of DNS servers in the domain is changed the Customer manually modifies the NS record in the zone.

The Customer makes changes to a zone via RU-NIC's web site at http://www.nic.ru as follows:

Any changes made by the Customer will come into effect no later than four (4) hours from the moment they are made.

5.4.2. The following changes in a zone are made automatically and come into effect no later than four (4) hours from the moment they are made:

5.6.1. On switching from the Primary-Auto Service to the Primary-Standard Service all records added to the zone during the use of the Primary-Auto service are retained.

5.6.2. Switching from the Primary-Auto Service to the Primary-Standard service is done automatically after the Customer has ordered and paid for the Primary-Standard service. The Primary-Auto service will then be suspended, its term will not change, and any money already paid for the service will not be refunded.

5.6.3. The Customer will be able to resume the use of the suspended Primary-Auto service at any time before the service term expires by following the procedure described in section 4.6.3 of this Schedule. After switching to the Primary-Auto service the Primary-Standard service will be temporally switched off by RU-NIC, its term does not change, and there is no refund. After switching to the Primary-Auto service the Primary-Standard service will be temporally switched off by RU-NIC, its term does not change, and there is no refund.

- log into the section "Manage your account";
- select "Review and update data" in the "Services" menu;
- find the service (Web-forwarding service for the domain);
- click on the "URL" link in the "Modify parameters" column;
- make necessary changes;
- save the changes.

7.4.1. Individual rules can be defined for forwarding individual e-mail addresses (one-to-one correspondence between an address to which e-mails are sent and an address to which they are to be forwarded during the provision of the service).

Only one individual mail forwarding rule can be defined for any e-mail address.

The total number of individual mail forwarding rules may be from 40 to 200, depending on the lengths of e-mail addresses.

7.4.2. One of the following two general rules can be set for e-mail addresses for which individual mail forwarding rules have not been defined:

If a general mail forwarding rule has not been set, e-mails sent to addresses for which individual forwarding rules have not been defined are deleted. Their senders will receive a message saying that the addressee is unknown.

- log into the section "Manage your account";
- select "Review and update data" in the "Services" menu;
- find the service (Mail-forwarding service for the domain);
- click on the "E-mail" link in the "Modify parameters" column;
- make necessary changes;
- save the changes.

7.6.1. Mail forwarding is only provided for the domain for which the service is ordered. It is not provided for subdomains of this domain.

7.6.2. If an e-mail is sent to multiple addresses in the domain for which the service is ordered, and the forwarding rules for these addresses dictate that the e-mail is to be forwarded to the same address, only one copy of the e-mail will be sent to that address.

7.6.3. The size of a forwarded e-mail may not exceed 10 MB. Any e-mail exceeding this limit will be rejected by RU-NIC's mail server without notice to both the sender and the Customer.

7.6.4. RU-NIC will not be liable for inability to forward an e-mail to the address specified by the Customer in the service settings due to circumstances beyond RU-NIC's control, for example:

7.6.5. If RU-NIC fails to forward an e-mail due to a reason described in section 7.6.4, RU-NIC will repeat its attempts to forward the e-mail every 30 minutes. Such attempts will be made for no more than four (4) days from the day the e-mail is received by RU-NIC's mail server. After this period the e-mail will be deleted and the sender will be sent a message saying the e-mail cannot be delivered.

7.6.6. The volume of the Customer's e-mails stored simultaneously on RU-NIC's mail server may not exceed 100 MB. If this limit is exceeded, RU-NIC's mail server will stop accepting the Customer's e-mails without notice to the senders and the Customer.

7.6.7. The service must not be used for:

7.6.8. If the Customer is in breach of section 7.6.7 of this Schedule, RU-NIC may suspend the provision of the service by giving the Customer a single notice via the standard communication channel. In such cases the service term will not be extended. The provision of the service will be resumed after the Customer has removed the cause of the suspension.