When a domain transfer is the relocation of a DNS domain to a new registrar called.

Motivation for such a shift is often dissatisfaction with service or pricing policies of the current registrar. Also, usually after corporate acquisitions or mergers of DNA by transfer of all domains into a single consolidated in Registrar. In November 2004, ICANN for domain-transfer rules set up, the registrars are binding for all and the process will simplify and make safer.

A domain transfer does not change the ownership of the affected domain . Ultimately, only the database entry in the registry change that defines which registrar for this domain and its owner is responsible.

End

The starting point is always the end user, ie the holder of the domain. His first contact is the future registrar, who will then contact the relevant registry with the current registrar at:

1. The registrant (End) authorizes and legitimizes the future compared to the registrar.
2. The registrant requested the Registrar to the future transfer of the domain to be displaced.
3. The future registrar shall transmit the request to the master registry (possibly after additional confirmation from the domain owners).
4. The Registry will contact the current registrar and request him to accept or decline to (within five days of no response, which is your approval).
5. The Registrar will send an e-mail to the administrative contact for the customer.
6. The administrative contact person confirming the transfer (leave out the confirmation, as does the rejection).
7. The current Administrar forwards the confirmation or rejection to the master registry.
8. The registry performs the transfer through change in its database.

If the transfer completed as a service via a third party (such as a hosting provider), it can act as a mediator between registrant and registrar and thereby settle some or all interactions with the participating registrars in the order. The registrant must leave him only the documents for identification and authorization.

In practice, this process is usually fully automatic. The only manual operations are the formulation of the transfer request (step 2) and the confirmation (step 6) by the end customer. The communication between the Registrar and Registrar parent is usually via the Extensible Provisioning Protocol .

There are, in some cases, additional security measures that an unauthorized domain transfer is to be prevented. In some domains (eg, org.. Info, de. Biz,.. Cn, com., Us.. La, net. Pl,.. Name) is to provide a so-called Authorization Codes to initiate a domain transfer is required. These 6 to 16 characters comprehensive sequence obtained on request from the current registrar. Some domains (eg. Com,. Net) may have the status Registrar-Lock are. Before any changes are possible, the current holder of a domain registrar cause of the status to Active set.

Conflicts

The theory in the clear and seemingly simple transfer process can be developed in practice into an administrative nightmare. Main reason for this is historical information contained in the domain database. Is about the administrative contact person left the company the domain owner already has a consent to transfer (step 6) is not easily possible.

Another potential problem is false or insufficient positioned Name Server represent the current Registrar for example, could have accepted that exists for a domain, contrary to Internet rules, only one name server, the future but requires at least two name servers and does not accept the transfer as a result.

As a registrar to a registered domain is little worthy of him (about $ 5 to $ 30 per year) is its readiness to litigation by consuming manual touch up resolve, naturally low. This is especially true for the current registrar, so losing a paying customer.