RU   EN
 
Schedule 1/3
to Service Agreement

Effective
June 20, 2011

Domains Maintenance Schedule

1. Definitions
2. General Terms and Conditions
3. Service Order
4. Service Renewals
5. Payments
6. Secondary Service
7. Primary-Standard Service
8. Primary-Auto Service
9. Web-forwarding Service
10. Mail Redirection Service
11. Domain Redirection Service

1. Definitions

The Contractor - Joint Stock Company "RU-CENTER". The Contractor's web server is located at http://www.nic.ru/

Customer - an individual or legal entity that applied to the Contractor for a domain maintenance service.

DNS - Domain Name System. Its main purpose is to map the domain names of devices to IP addresses and vice versa - IP addresses to domain names. The basis of the DNS is a distributed hierarchical database.

Domain - in the DNS, an autonomously administered area of the domain name space.

Domain name - the identifier of a record in the DNS database, which is usually in the form of several labels separated by dots.

Zone - the set of records about the resources and domains of the next (lower) level located within a single domain.

DNS server - a program that stores one or several DNS zones and serves queries to the DNS database.

Primary DNS server - the DNS server that stores complete reference information about the zone.

Secondary DNS server - the DNS server that receives the information of the zone from another DNS server.

URL (Uniform Resource Locator) - is the string specifying the method and route of access to a resource on the Internet.

Order - a request from the Customer to the Contractor, in a form determined by the Contractor, that contains all the data required for the provision of a service.

Agreement Account - the set of data on the Customer's payments to the Contractor as well as the services the Contractor has provided to the Customer. Any payment made by the Customer is credited to their Agreement Account after the money has been credited to the Contractor's bank account and the Contractor has received from the bank a document identifying the payment.

Notice. The terms omitted in this Schedule are given in the Domains Registration Schedule in RU TLD (Schedule 1/1 to the Service Agreement).


2. General Terms and Conditions

2.1. The Contractor is operating under and in accordance with license No. 46650 issued for the provision of telematic services of telecommunications.

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

2.3. Submission of the Customer's Data for the Agreement

2.3.1. 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.3.2. In the case of any doubt as to the authenticity of the information provided by the Customer, the Contractor 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.3.3. 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 the Contractor sends the first request, the Contractor may:

  • refuse the Customer's request for a new service;
  • suspend the provision of services to the Customer;
  • refuse the Customer's request for the renewal of a service.

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 the Contractor sends the first request, the provision of services to the Customer can be terminated.

2.4. The Customer and the Contractor acknowledge the legal effect of notifications and messages, sent by the Contractor to the Customer's e-mail addresses, specified by the Customer in the Service Agreement and other documents. Such notifications and messages are equal to messages and notifications in writing, sent by the Contractor to Customer's mail addresses. The Customer and the Contractor, in case of any disagreements concerning the facts of sending and receiving messages, the time of sending, contents of the messages, agreed to consider evidences of the Contractor's archive service binding and definitive for settlement of disputes between indicated parties.

2.5. The Customer shall follow requirements of Terms of Use which are available at the Contractor's server http://www.nic.ru/about/en/servpol.html. The Customer agrees that he could be affected by consequences of actions applied by the Contractor for prevention of the adverse effects of third party activity impairing the operation of the Contractor Service system. In its actions the Contractor follows provisions of Terms of Use and guarantees the minimization of such adverse effects to the Customer.

2.6. An Order for a service of domain name registration confirms that the Customer agrees to pay for the service at the price effective at the date the processing of the Order begins.

2.7. Domain maintenance service is delivered to the Customer for a one year period. Term of the service validity may be extended for the next year at a Customer's discretion.

2.8. The Contractor will notify the Customer of the fact that the service has been provided by e-mail. If the motivated Customer's objections set forth in simple language in writing and sent by mail service failed to reach the Contractor's address within 15 (fifteen) calendar days from the date of the abovementioned Contractor's e-mail, the service rendered to the Customer by the Contractor is considered to be accepted by the Customer.

2.9. The Customer and shall not use the service in a way that does not comply with the Russian Federation's legislation, including disseminating and advertising pornographic materials, instigating violence, extremist activities or the overthrow of government etc., as well as in a way that is inconsistent with the public interest and the principles of humanity and morality, offends human dignity or religious feelings etc.

2.10. If the Customer is in breach of section 2.9 of this Schedule, the Contractor 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.

2.11. The service term can be suspended by the Contractor without prior notice in cases which caused or may cause, in the Contactor's opinion, disruption or threat of disruption of the Contractor's servicing system functioning.

2.12. The Contractor will not be liable in connection with the use of domain names for which the Contractor's services are ordered, as well as for the content of information resources to which requests are redirected during the provision of the services.

2.13. The total time the Contractor fails to provide a service in a single month will not exceed one (1) hour per month.

2.14. From October 19, 2010 no more Orders for the web-forwarding service will be accepted by the Contractor.

2.15. In view of delivery of domains maintenance services, for technology-motivated reasons, the Contractor is entitled to change network names and IP addresses of DNS servers with the service quality remaining unaffected.

2.16. If the domains maintenance service has been delivered for the domain, which contains, among other things, the Contractor's DNS servers, and paid for under the contract entered into between the Customer and Contractor, the latter is entitled, for technology-motivated reasons, to independently change the list of DNS servers for this domain, provided its functionality is not affected.

3. Service Order

3.1 Services are ordered on the Contractor's web site.

3.2. An Order will be deemed ready-to-execute and gets in processing, once the funds in the Customer' personal account are sufficient to pay for all services in the Order. Any Order that cannot be processed within 3 months will be deleted.

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

3.4. If any one of the Primary-Standard, Primary-Auto or Secondary services 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.

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

3.6 Orders execution procedure

3.6.1. The Contractor will process any Orders for new services on a first come - first serve basis. The sequence in which new Orders are processed can be changed on the Contractor's web site in the "Manage your account" section ("Orders", the "Processing queue, order removal" link);

3.6.2. The 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 (the funds for a service whose term expires earlier are blocked earlier), if otherwise is stated by the Customer for the use of electronic system for payments. In this case the service renewal procedure will be established by the Customer as scheduled by the e-payment systems.

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

3.7 An Order for a service may only be cancelled before its processing begins. The Customer can cancel an Order on the Contractor's web site in the "Manage your account" section ("Orders", the "Processing queue, order removal" link).

4. Service Renewals

4.1. The Contractor 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 that are in use and which renewal has not been declined by the Customer, are allocated under the procedure specified in p. 3.6.2, 3.6.3 hereinabove.

4.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. The Contractor 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.

4.3. Funds for a service renewal are allocated automatically by the Contractor 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 the Contractor 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.

4.4. On the Customer's initiative the funds are allocated on and withdrawn from his/her Service Agreement personal account for service renewal by the Contractor before the terms specified in the paragraph 4.3 hereinabove, but not earlier than 2 (two) months before the service expires. In such case funds allocation and withdrawal will be made within 24 hours since the Customer's consent to pay in advance for service renewal is received by the Contractor. The Customer can confirm his agreement for ahead of schedule service renewal payment on the Contractor's web-server in the section "Manage your account" ("Services", the link "Services renewal").

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

4.6. The provision of a service will be suspended if it is not renewed by the Customer before the expiry of the service term. The Contractor will terminate the provision of a service, if the Customer fails to renew it within thirty (30) calendar days after the service term expiry.

5. Payments

5.1. The fees for the Contractor's services are fixed in Addendum 2 to the Service Agreement("Pricing").

5.2. Invoicing:

The Contractor will generate an invoice after the Contractor receives the Customer's request for the invoice. Invoices can be requested via the Contractor's web site in the "Manage your account" section ("Payment", the "Recharge your account" link). If the Customer has entered into a Agreement with the Contractor, the original of the invoice is sent to the Customer by post:
- if the Customer is an organization or a sole trader - not later than three (3) working days after the Contractor receives the Customer's request for the invoice;
- if the Customer is an individual - at the Customer's request, sent via the standard communication channel to the Contractor's customer service.

The Customer can print a copy of any issued invoice from the Contractor's web site in the "Manage your account" section ("Payment", the "Bills issued" link).

5.3. When making a payment, the Customer shall indicate the number of the Agreement with the Contractor on the payment documents.

5.4. The Contractor 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 the Contractor's bank account and the Contractor has received from the bank a document identifying the payment.

The Customer can access the information of their Agreement Account on the Contractor's web site in the "Manage your account" section ("Payment", the "Account balance" link).

5.5. On termination of the Agreement the Contractor will refund the Customer's unused balance by bank transfer to the Customer's bank account at any bank resident in the Russian Federation. The Contractor will take steps to complete the refund within ten (10) working days from the day the Customer submits a written request for the refund with the full bank details of the recipient.

5.6. There will be no refund of the fee for any unexpired period of a cancelled domain name registration.

5.7. Customer's obligations for services payment will be deemed unexecuted, if he (she) made a refund upon the request of the payment system, by which the Customer paid for the service. In this case the Contractor is entitled to suspend the service for the Customer since the moment of refund.

6. Secondary Service

The Secondary service consists in configuring the Contractor's hardware as secondary DNS servers for the domain specified by the Customer.

6.1. For this service the Contractor uses the hardware configured to operate in two secondary DNS servers mode, which network names and IP addresses are published on the Contractor's web server in the 'Secondary' service section.

6.2. The service is considered provided to the Customer after the Contractor's hardware has been configured as secondary DNS servers for the domain specified by the Customer according to the DNS standards.

The Contractor's hardware will start operating in the above mode not later than twelve (12) hours after the service is provided.

6.3. Essential Requirements for the Server Specified in the Service Settings as the Primary DNS Server

a) DNS server must be configured as the primary or a secondary DNS server for the domain specified during service order according to the DNS standards, and must be connected to the Internet.
b) DNS server's settings must allow transfer of the zone of the domain specified during service order by the requests from the IP addresses of the Contractors secondary DNS servers.

If, during the provision of the service, the Contractor finds errors in the configuration of the server indicated as the primary DNS server, the Contractor will notify the Customer of them by e-mail via the standard communication channel.

6.4. Zone Transfer to the Contractor's secondary DNS Servers

6.4.1. The Contractor's DNS server will request the specified primary DNS server for zone transfer from the moment the provision of the service begins.

6.4.2. If the zone cannot be transferred by the Contractor's DNS server because the requirements defined in section 6.3 hereunder are not met, the Contractor's DNS server will repeat its requests for zone transfer for four (4) calendar days, whereupon the requests will cease. The Customer may prematurely promote zone transfer process by the Contractor's DNS server under the procedure given on the Contractor's web server in 'Secondary' service section.

6.5. Updating Zone on the Contractor's DNS Servers

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

6.5.2. If zone transfer to the Contractor's DNS server is not possible because the requirements defined in section 6.3 hereunder are not met, the Contractor's DNS server will repeat its requests for zone transfer with the "Retry" frequency for the "Expire" period.

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

The Customer can manually promote zone transfer to the Contractor's DNS server under the procedure given on the Contractor's web server in 'Secondary' service section.

6.6. Changing Secondary Service Settings (by the Customer)

Changing the DNS-server IP-address, specified in the service settings as primary, and changing IP-addresses list, for requests from which the Contractor's DNS servers do not deny zone receiving, is made on the Contractor's web-server under the procedure given on the Contractor's web server in 'Secondary' service section

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

7. Primary-Standard Service

The Primary-Standard service consists in configuring the Contractor's hardware as the primary DNS server for the domain specified by the Customer and offering the Customer the opportunity to make changes to the zone.

7.1. For this service the Contractor uses the hardware which network names and IP addresses are published on the Contractor's web server in the 'Primary-Standard' service section.

7.2. The service is considered provided to the Customer, once the Contractor fulfilled the below steps:
- the Contractor's hardware has been configured as the primary DNS server for the domain specified by the Customer 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 Contractor's hardware will start operating in the above mode not later than twelve (12) hours after the service is provided.

7.3. In the provision of this service the Contractor will automatically create the Customer's zone using the information provided by the Customer in the Agreement and on the Order:
- SOA-record shall contain the e-mail address specified in the "mnt-nfy" field of the Agreement, or, if this field is empty - address specified in 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, 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.

Any subsequent changes to the zone are made manually by the Customer following the procedure defined in paragraph 4.4 hereinabove.

7.4. Making Zone Changes

7.4.1. Changes are made by the Customer, using the zone file editor, provided by the Contractor. The editor can be accessed under the procedure given on the Contractor's web server in 'Secondary' service section.

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

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

7.4.3. The Customer can make changes in the zone and change the contents of resource records for the direct and reverse domains listed on the Contractor's web server in the 'Primary-Standard' service section.

The changes introduced by the Customer become effective in not more than 4 (four) hours after they have been made.

7.4.4. The Contractor is not liable for the consequences of any errors made by the Customer when adding records to a zone.

7.5. The List of IP Addresses Authorized for Zone Transfer from the Contractor's DNS Server is modified under the procedure given on the Contractor's web server in 'Primary-Standard' service section.

7.6. Switching from the Primary-Standard to the Primary-Auto Service

7.6.1. On switching from the Primary-Standard service to the Primary-Auto service:
- all records added by the Customer to the zone during the use of the Primary-Standard service are deleted;
- new records required for the provision of other services ordered by the Customer (domain registration, Secondary, Web-forwarding) are automatically added to the zone.

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

7.6.3. If the Primary-Standard service is disabled due to the reason specified in p. 7.6.2 hereinabove the Customer may enable it at any moment before the service expiry date and then restore any of the earlier saved zone files.

The service is enabled under the procedure given on the Contractor's web server in the 'Primary-Standard' service section.

After enabling the Primary-Standard service the Primary-Auto service will be temporally disabled by the Contractor with no refund and expiry date change.

8. Primary-Auto Service

The Primary-Auto service consists in configuring the Contractor's hardware as the primary DNS server for the domain specified by the Customer. This service includes the automatic addition to the zone of records required for the provision of other services ordered by the Customer (domain registration, Secondary, Web-forwarding).

8.1. For this service the Contractor uses the hardware which data are published on the Contractor's web server in the 'Primary-Auto' service section.

8.2. The service is considered provided to the Customer after the Contractor's hardware has been configured as the primary DNS server for the domain specified by the Customer according to the DNS standards and if the server's settings 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 Contractor's hardware will start operating in the above mode not later than twelve (12) hours after the service is provided.

8.3. In the provision of this service the Contractor will automatically create the Customer's zone:
- the e-mail address in the SOA-record will be the Contractor'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, 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.

Any subsequent changes to the zone are made automatically in accordance with paragraph 5.4 hereinabove, except for cases when the service is ordered for a domain not administered under the Customer's Agreement. In such cases NS-records are modified manually by the Customer.

8.4. Making Zone Changes

8.4.1. The Customer will independently make changes into NS-record zone, when changing the list of DNS servers in the domain, if this domain is not administered under the Customer's Agreement.

The Customer makes zone changes on the Contractor's web server under the procedure given on the Contractor's web server in 'Primary-Auto' service section.

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

8.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:
- modification of the NS-record of a domain that is administered under the Customer's Agreement, when the list of DNS servers in the domain is changed;
- all necessary changes when the Customer orders other domain maintenance services (Secondary, Web-forwarding);
- deletion of records after the term of other domain maintenance services (Secondary, Web-forwarding) expires.

8.5. Modifying the List of IP Addresses Authorized for Zone Transfer from the Contractor's DNS Server

The list can be modified by the Customer on the Contractor's web site following the procedure described in section 8.4 hereinabove.

8.6. Switching from the Primary-Auto Service to the Primary-Standard Service

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

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

8.6.3. If the Primary-Auto service is disabled due to the reason specified in p. 8.6.2 the Customer may enable it at any moment before the service expiry date. The service is enabled under the procedure specified in p. 7.6.3 hereinabove. Once the Primary-Auto service is enabled the Primary-Standard service will be temporarily disabled by the Contractor, with no refund and expiry date change.

9. Web-forwarding Service

The Web-forwarding service consists in configuring the Contractor's hardware to redirect HTTP requests for a domain to URL specified in the service settings.

9.1. For this service the Contractor uses hardware, which data are published on the Contractor's web server in the 'Web-forwarding' service section.

9.2. The service is considered provided to the Customer after the Contractor's hardware has been configured to redirect HTTP requests for the domain, for which the service is ordered to URL indicated in the service settings.

The Contractor's hardware will start operating in the above mode not later than twelve (12) hours after the service is provided.

9.3. For this service to function, the following A-record in the format specified by the Contractor and determined in para 9.4 hereinbelow must be added to the zone.

If the Contractor delivers the Primary-Auto service for the Customer, the A-record is added to the zone automatically.

9.4. If the Customer does not use the 'Primary-Auto' service for the domain, for which 'Web-forwarding' service has been delivered, to enable functioning of the 'Web-forwarding' service, he/she shall independently add À-record into the zone, which format is published on the Contractor's web server in the 'Web-forwarding' service section.

9.5. URL for redirection of the Customer's domain queries will be changed by the Customer on the Contractor's web server under the procedure given on the Contractor's web server in 'Web-forwarding' service section.

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

10. 'Mail Redirection' Service

The 'Mail Redirection' Service consists in configuring the Contractor's hardware to forward e-mail messages to the e-mail addresses indicated in the service settings.

Electronic mail address (e-mail address) has the following format: user@domain, where user is a user name and domain - a domain name.

10.1. To deliver the service to the Customer the Contractor uses the hardware enabling redirection of the electronic letters, as well as same configured for operation in primary and secondary DNS server mode for the domain specified by the Customer.

Network names and IP addresses of the hardware utilized in the above purposes are published on the Contractor's web server in the 'Mail redirection' service section.

The Contractor's hardware starts functioning in the specified modes not later than in 12 (twelve) hours since the service delivery moment.

10.2. The service is deemed rendered after the Contractor configures its hardware for the e-mails redirection mode for the domain for which the 'Mail Redirection' service was ordered. For services delivery the Contractor hereby uses the rules established by the Customer in the service settings.

10.3. For service functioning the zone shall contain MX-record in the format specified by the Customer as defined in para 10.4. If the Customer uses DNS servers specified in para 10.1 hereinabove, the required MX-record shall be added to the zone automatically.

The Contractor guarantees proper functioning of the service, if the Customer uses DNS servers indicated in p. 10.1 hereinabove


10.4. If the Customer does not use the Contractor's DNS servers specified in p. 10.1 hereinabove for the domain, for which the Mail Redirection service was delivered, for proper functioning of the service he/she shall independently add MX-record into the zone, which format is published on the Contractor's web server in the 'Mail Redirection' service section.

10.5. Maximum forth-level domains may be subjected to the 'Mail Redirection' service.

10.6. The 'Mail Redirection' service may be delivered only for the registered domain name. Service Order for a free domain name means Customer's consent with the domain name registration on his/her name and funds withdrawal for the registration service from the personal account. If the specified domain name is not registered on the Customer's name for some reason, the Contractor will not deliver the 'Mail Redirection' service.

10.7. The 'Mail Redirection' service may be suspended by the Contractor at the Customer's discretion. In this case its validity term will not change and the money will not be refunded.

10.8. If the 'Mail Redirection' service is disabled for the reason specified in p. 10.8, the Customer may enable it at any time before its expiry period.

10.9. Service Options

Mail redirection is provided for e-mail addresses in the domain for which the 'Mail Redirection' Service was ordered.

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

10.9.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:
a) any e-mail addressed to the domain is redirected to an address with the same user name within another domain (except for e-mails sent to addresses for which individual forwarding rules have been specified);
b) all e-mails addressed to the domain are redirected to a single e-mail address (except for e-mails sent to addresses for which individual forwarding rules have been specified).

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.

10.10. Mail Redirection Rules are changed by the Contractor under the procedure given on the Contractor's web server in the 'Mail Redirection' service section.

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

10.11. Special Conditions

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

10.11.2. If an e-mail is sent to multiple addresses in the domain for which the service is ordered, and the redirection rules defined by the Customer for these addresses dictate that the e-mail is to be redirected to the same address, only one copy of the e-mail will be sent to that address.

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

10.11.4. The Contractor will not be liable for inability to redirect an e-mail to the address specified in the service settings due to circumstances beyond the Contractor's control, for example:
a) DNS servers of the domain to which the e-mail is to be redirected do not operate in accordance with the DNS standards, are not connected to the Internet, and/or do not have in the zone the records required for the delivery of the e-mail to the domain;
b) the mail server of the address to which the e-mail is to be redirected is not accessible via the Internet or does not accept e-mails sent by the Contractor;
c) a mail server that is not owned by the Contractor and is on the e-mail's route is down or configured in a way that prevents the delivery of the e-mail or causes corruption of its content.

10.11.5. If the Contractor fails to redirect an e-mail due to a reason described in section 10.11.4, the Contractor will repeat its attempts to redirect 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 the Contractor'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.

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

10.11.7. The service must not be used for:
a) mass distribution of unsolicited e-mails; "mass distribution" is understood here as both distribution to multiple recipients and repeated mailing to a single recipient;
b) unsolicited distribution of e-mails exceeding 5 KB (including overhead information);
c) unsolicited distribution of advertising, commercial or promotion e-mails, as well as e-mails containing material inconsistent with the public interest and principles of humanity and morality (in particular, e-mails containing obscene language, instigating violence, extremist activities, overthrow of government, or inhumane acts, or offending human dignity or religious feelings etc.);
d) off-topic posting to web conferences; "web conference" is understood here as a Usenet conference (news group) or other web conference, forum or electronic mailing list;
e) posting to a web conference of advertising, commercial or promotion messages, except when such postings are explicitly allowed by the conference's rules or authorized by the conference's moderator;
f) posting to a web conference of messages with attached files, except when such attachments are explicitly allowed by the conference's rules or authorized by the conference's moderator;
g) mailing of information to recipients that have previously explicitly expressed their desire not to receive such information.

10.11.8. If the Customer is in breach of section 10.11.7 hereinabove, the Contractor 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 and the Customer addresses the Contractor over the communication channel.

11. 'Domain Redirection' Service

The 'Domain Redirection' service consists in configuring the Contractor's hardware to redirect HTTP queries to the domain on the URL indicated in the service settings.

11.1. For this service the Contractor uses the hardware configured to redirect HTTP queries to the domain, as well as same configured to operate in two secondary DNS servers mode for the domain specified by the Customer.

Network names and IP addresses of the hardware utilized in the above purposes are published on the Contractor's web server in the 'Domain redirection' service section.

The Contractor's hardware starts functioning in the specified modes not later than in 12 (twelve) hours since the service delivery moment.

11.2. The service is deemed rendered to the Customer after the Contractor configures its hardware for HTTP queries redirection to the domain, for which the 'Domain Redirection' service was ordered. For this purpose the Contractor hereby uses the rules established by the Customer in the service settings.

11.3. For the service functioning, the zone shall contain A-record in the format specified by the Customer as defined in para 11.4 hereinbelow. If the Customer uses DNS servers specified in para 11.1 hereinabove, the required A-record shall be added to the zone automatically.

The Contractor guarantees proper functioning of the 'Domain Redirection' service, when using DNS servers indicated in p. 11.1.


11.4. If the Customer does not use the Contractor's DNS servers specified in p. 11.1 hereinabove for the domain name, for which the 'Domain Redirection' service was delivered, for proper functioning of the service he/she shall independently add A-record into the zone, which format is published on the Contractor's web server in the 'Domain Redirection' service section.

11.5. Maximum forth-level domains may be subjected to the 'Domain Redirection' service.

11.6. The 'Domain Redirection' service may be delivered only for the registered domain name. Service Order for a free domain name means Customer's agreement with the domain name registration on his/her name and funds withdrawal for the registration service from the personal account. If the specified domain name is not registered on the Customer's name for some reason, the Contractor will not deliver the 'Domain Redirection' service.

11.7. URL for redirection of the queries to the domain names are changed by the Contractor under the procedure given on the Contractor's web server in 'Domain Redirection' service section.

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

© Regional Network Information Center (RU-CENTER), 2001—2012