Transfer-in (change of Registrar)

(Difference between revisions)
Jump to: navigation, search
(Basic steps to transfer the domain name via API)
Line 89: Line 89:
3) Create a contact for the owner (Field "isOwner" = 1) and provide the needed additional fields corresponding to the semantics rules.
3) Create a contact for the owner (Field "isOwner" = 1) and provide the needed additional fields corresponding to the semantics rules.
Remember that a contact owner can be used only for one domain name.

Latest revision as of 16:38, 3 March 2017


[edit] Transfer via our website

A reseller can order a domain name registration directly into our website by using his reseller account and, thus, benefit for our online checkout process and its wizard.

At the final step, he will have to approve the order and the corresponding operations will be created automatically.

[edit] Transfer via l'API

By using the API, a domain transfer is requested with the function domainTransferIn.

The function requires the following parameters:

Format Variable Description Notes
string (32) idSession identifier of the session
string (255) domain domain name to be transferred
string (64) authID Authorization code ifapplicable
string (12) idOwner identifier of the owner contact Peut être #AUTO# ou un identifiant avec "isOwner=1
string (12) idAdmin identifier of the technical contact avec "isOwner=0"
string (12) idTech identifier of the billing contact avec "isOwner=0"
string (12) idBilling Identifiant du contact facturation avec "isOwner=0"
string (255) ns1 DNS name server 1
string (255) ns2 DNS name server 2
string (255) ns3 DNS name server 3
string (255) ns4 DNS name server 4
string (255) ns5 DNS name server 5

[edit] Semantic rules

Registration rules are different according to the Tlds. See procedure, restrictions and rules Category:Tld

An authorization code can be necessary
Restrictions may apply and / or additional information may be necessary for contacts
2 nameservers can be required and, sometimes, a successfull zonecheck is needed before the transfer

Whatever the process used to register a domain name, the Reseller should know the semantic rules of the extension .

The field "IdOwner" can accept a contact ID or the term "#AUTO#"

In the first case, you must provide a contact ID that is defined with the exact name / surname or
organization name of the current owner
In the second case, the owner will be retrieved automaticaly if the transfer succeeds. If the field
accepts "#AUTO#" for the corresponding tld, any contact ID provided will not be took into account. In
any case, it is not possible to change the owner during an ingoing transfer

When you call the domainTransferIn function, the API checks only if the mandatory fields are provided. We check the semantic rules only when the operation is processed, given that we perform the needed verification before requesting the registration to the registry. Therefore the operation may generate an error (Invalid authorization code, protection against transfer enabled, etc.)

[edit] Special Notes for generic extensions

According to ICANN procedure, the gaining registrar must contact current owner or administrative contact so they can confirm the transfer (this is called Forms of authorization (FOA))

For these extensions, NETIM it will be indicated in the notification sent as

NETIM as "Gaining Registrar"

[edit] Basic steps to transfer the domain name via API

1) For the extension to be registered, check the semantic rules of the domainTransferIn function and the possible values to determine:

 the number of nameservers required
 if a successful zonecheck is required
 Any restrictions on contacts
 if an idOwner is required or #AUTO
 if the authid is required

2) If a zonecheck is required, ensure that the new domain name is installed onto its nameservers according to the technical rules of the registry.

We provide an online tool to test this:

3) Create a contact for the owner (Field "isOwner" = 1) and provide the needed additional fields corresponding to the semantics rules.

4) Possibly create a contact for administrative / technical / billing contacts if necessary (Field "isOwner" = 0).

You can use your Reseller account handle

5) Request the registration, by using the domainTransferIn function

The API will perform a first check to see if all provided datas are OK (contacts are existing and are belonging to you, nameservers are existing, and so on...)

You receive a tracking number for the request and you can now follow its status

6) Netim makes the domain transfer according to the registry's procedure. Therefore different actions may be necessary as the provision of identification documents or forms Un numéro d'opération est retourné pour le suivi

[edit] Transfer OUT

During an outgoing transfer, a domain name is transferred from Netim to another registrar. This kind of operation is requested by the gaining registrar.

For some extensions the registrar-lock feature is available. In the present case, it is necessary to disable it.

If the protection is enabled, i.e the domain name is locked, Netim will automaticaly reject any transfer
requests from another registrar. 
Otherwise, if the protection is disabled, Netim will automaticaly accept them during the corresponding procedure.
Personal tools

Your account
Domain names
Shared Hosting
Old Hosting offers
SSL Certificates
Contact Us