good day

Moved from one registrar to another (only domain names)

When transferring all the settings were reset and our sites and services stopped working. Tell me, is this a common practice (i.e., any relocation cuts down sites for a period of up to 2 days) or is there an error from the transmitting registrar (it was he who reset the settings and did not transfer them to the target registrar)? Is it possible to "smooth" registrar change?

    3 answers 3

    Typically, registrars allow you to specify your DNS server. If you do not want problems when moving (or when the registrar downtime), then you should divide the DNS and domain registration itself in advance:

    1. Take a third-party DNS service - Amazon Route 53 , for example - it is a penny.
    2. Transfer all entries to it.
    3. Change the nameserver in the domain settings from the logger to the Amazon server for the domain. Wait for the changes to take effect.
    4. When you move from a new registrar, specify the same Amazon servers.

    Then the registrar change will take place without downtime.

    If the new registrar does not allow to specify third-party DNS servers when moving, then you should not move to it at all.

      Replacing DNS takes time. This is usually done for a few hours. But you can also "move" painlessly. For this you need:
      Connect the site in the control panel.
      The HTTPD settings display the IP address that is used for this site. Create a temporary A-record on your existing DNS server for your domain, for example

      new.site.ru. IN A 123.45.67.89

      (where "site.ru." is the name of your site, and "123.45.67.89" is your IP address) In the HTTPD settings, in the ServerAlias ​​field, add the name new.site.ru
      Upload all the necessary files via FTP.
      If necessary, create a database and transfer the data. Make sure that the new site opens at new.site.ru and is fully functional.
      If your site has dynamic content that is constantly changing, you must pause the site to transfer the latest relevant data. You can do this, for example, using .htaccess:

       <Files *> Order deny,allow deny from all </Files>

      Then transfer all current data, including files and databases, to hosting. Forward from old hosting using .htaccess:

       RewriteEngine On RewriteRule (.*) http://new.site.ru/$1 [R,L,QSA]

      Change the DNS servers for your domain to new ones.

      • the site itself was not physically perezzhal, the hoster remained the same. Only the domain registrar has changed. It was assumed that the new registrar at the hour X will take over the rights to the DNS record and all the settings. - Shadow76
      • Replacing DNS does not happen instantly. Nothing can be done about it. 2 days is a lot. Usually, everything changes within 2 hours. If you moved to another hosting, you could do the trick I described above. Display the site on the old DNS until it changes and immediately picks up the new hosting. And so, just wait. - Raftko
      • the correspondence of the name and the address remained the same, just another registrar became the “keeper” of the master record. the problem is that when you move, all the settings were cleared first (linking the host to the IP), it all went off to the clients (the site became unavailable), then, while re-typing the settings from the new registrar, they went over the network .... Of course, most customers saw changes in those two hours, but some problems with name resolution remained about a day and a half - Shadow76

      For greater "smoothness" in such moves, I would recommend not using the dns hosting service provided by the registrar, but:

      • either keep your own DNS servers (at least two, either separated geographically or connected via different Internet providers);
      • or use the services of a dns hosting from a third-party dns provider (it is better if there are more than one of them);
      • or combine: your dns-server and third-party dns-provider.