Registrar's Information Space
Table of contents All topics
There are some differences in the new registry system compared to the old one, regarding how contact objects are created and handled. Here are the main differences:

  • When a registrar is replaced, all contacts will be copied automatically.
  • The system will create the corresponding objects for the new registrar.
  • If a registrar does not name a created contact (e.g. in the case of a change of registrar, or the registrar does not select one when creating a contact in the Registrar's Portal), the system will do it automatically. The first part of the object name is the name of the registrar, separated from the following part by an automatically generated string. (Example: RNAME:6257D24F)
  • If a registrar chooses an object name, the system will prefix it with the name of the registrar, if the name of the registrar is not already the first element of the chosen name. The allowed characters are the ASCII alphabet, numerals, ':' and '-‘, the max length is 100 characters. All entered letters will be saved as uppercase letters.
  • In the case of some changes, like the changing (chg) of the registrant (contact object) or the updating of mail addresses of contact persons, a confirmation and/or notification message is sent to the contact's mail address, which is also the basis for finishing the operations that need confirmation. Therefore, the accuracy and functionality of the contacts' mail addresses are even more important than before.

When contact data are edited, should the object of the contact be edited or replaced?

If the ident field does not change, there is no need to replace the object itself. It is only important in the case of a change in the contact data of the registrant, as the system will interpret the replacement of the registrant's object as a change of registrant; even if the person in the object is the same. Therefore, if it is only an address or phone number which changes, only the contact's object should be updated.

Why won't the system allow editing the data of a domain or a contact?

The domain may have statuses that prohibit it (updateProhibited, pendingUpdate). The former of these two is administratively assigned, usually in the course of a procedural act like court proceedings or a deletion procedure. The latter means that an updating procedure has already been started and is waiting for completion, and no new update queries can be made before that finishes.

If it is not due to the status directly prohibiting the update, it is likely that the present (contact) data are faulty or incomplete. Detailed reasons will also show up in the error message.
<Why can the ident field of a contact not be edited?>

Editing the ident field would change the named person of the contact. If the person changes, a new contact object should be created. There are only two exceptional cases when changes concerning the ident field are allowed:

  1. If the type (attribute 'type') of the ident field (element <eis:ident>) is 'birthday' and the date format is incorrect (YYYY-MM-DD);
  2. If the country code (attribute 'cc' of the element <eis:ident>) is missing.
In other cases a new contact object has to be created for updating the data even if the contact person remains the same.

NOTE! In the case of a registrant's contact, the system will interpret the replacement of a contact's object as a change of registrant and a confirmation mail will be sent to the registrant's mail address and the operation will not be concluded unless an answer is received.

In which cases will the system send notifications to the contact's mail address?

The system will send out notifications in the case of a change of mail address, when the domain is being transferred to another registrant and in the case of a deletion query. In the cases of transfer and deletion of the domain, a confirmation mail will also be sent to the (current) registrant's mail address with a web link that can be used to either confirm or reject the pending operation.

The registry system will also send a one-time automated notification to all the contacts of an expired domain one day after the expiration.

What should be done if the registrant cannot answer the confirmation mail, but the registrant's intent has been verified?

If the registrar has established the registrant's intent, the verified='yes' parameter can be used in the update or delete query, in which case the desired operation will be performed at once, instead of sending the confirmation mail and assigning the pendingUpdate or pendingDelete status.

How can I use the verified='yes' parameter in the Registrar's Portal?

The web interface does not offer the functionality of switching this parameter on. To use it, the registrar will have to submit a query composed by themselves. Manually composed queries can be submitted through the Registrar's Portal using the <XML console>.