DOT BE Transfer

There are going tobe a few changes in the transfer procedure. The old procedure is slow and involves alot of work for all parties.

What are the main changes?

  • the distinction between an ordinary transfer (simple change of registrar) and a trade (change of registrant, with or without a change of registrar) disappears. There will be just one transaction for both trades and transfers. The major benefit for registrars, of course, is to no longer have to wonder about the type of transaction you need to enter into the system in order to make the change required by the customer. This also means the risk that DNS.be may refuse the transaction because it is not the correct type, disappears completely.
  • The actual transaction will also be separated from the registrant’s permission, which means there will no longer be a delay factor in dealing with the transaction itself. In the current procedure, permission is only asked from the registrant after the transaction has been initiated. This may cause a delay (lack of approval, refusal of the transaction by DNS.be, the registrant does not receive a confirmation e-mail) and the registrar may remain unaware of the transaction until the expiry date is reached. In the new system, approval takes place in advance and the transaction is completed at the moment as it is entered.
  • The new procedure will also fundamentally change the way DNS.be works. There will be no more manual follow-up of transfer transactions set in motion. It will also mean an end to the system of confirming transfers by fax.
  • Finally, it will no longer be possible to schedule a transfer on a future date (transfer date).

  • Registrants wishing to move their domain name to another registrar or a new registrant wishing to take over the name from the current registrant, contact the new registrar.
  • The new registrar then asks DNS.be to send out a transfer code to the current registrant.
  • The registrant sends the code to his or her registrar or to the party taking over the domain name (who then sends the code on to his or her registrar).
  • The new registrar sets the transfer in motion and the internal application at DNS.be simply checks to see whether the code provided corresponds with the domain name for which the transfer is being requested. If the code-check is positive, the transfer is completed immediately and the old registrar is notified of the change.

What happens if the transfer code sent out does not reach the registrant?

There may be various reasons for this, e.g. the e-mail address given no longer exists, or the e-mail address does not belong to the registrant, but to another party (registrar, reseller, third party). If that happens, the registrant will have to ask his or her current registrar to modify the e-mail address. Once this update has been carried out, the procedure described above can be set in motion without any problem.

If DNS.be receives an error message after sending out the code, the new registrar will be notified immediately and can then contact the customer for the purpose of modifying his or her e-mail address.

What happens if the current registrar refuses to cooperate and does not modify the e-mail address?

In the new version of the registrar agreement, this type of situation has been anticipated so that it can be avoided as much as possible. However, if the registrant is faced with this problem, he or she will need to notify the legal department at DNS.be. After examining the case, the legal department may itself proceed with the update to the e-mail address. In that case, the registrar will receive a specific penalty. In the event of repeated problems, DNS.be may decide not to work with this registrar anymore.

Post to Twitter

2 Responses in other blogs/articles

  1. […] DOT BE Transfer « Riding the IDN train […]

  2. […] Home.DE dropcatching.IO RegistrationccTLD for sale: Misc.ccTLD for sale: NLContact MeDOT BE TransferDOT ES TRADEgTLD for sale.How to backorder a .DKName server checkRequest your EPP CODERogue […]

Leave a Reply

Your email address will not be published. Required fields are marked *


*