Will the site be unavailable when changing DNS servers?

D

Diversia2020-08-02 15:41:17

Domain Name System

Diversia, 2020-08-02 15:41:17

Hello.

There is a domain registered in reg.ru, which uses Yandex DNS (Ya.Connect). I want to transfer back to reg.ru. If you switch DNS servers and quickly make new entries in reg.ru, will the site be unavailable for some time? Does anyone have practical experience with such manipulations? Please share your experience.

Reply

Answer the question

In order to leave comments, you need to log in

5 answer(s)

I

Ivan Shumov, 2020-08-02
@inoise

There is always a lag when changing DNS. Which one - depends more on luck because the DNS system is distributed with caching in each node, including end machines.

Y

Yakov, 2020-08-02
Svetsky @jamessvetsky

Change NS records to reg ru. Until the root zone is updated, requests will go to the Yandex DNS servers. This is usually one and a half to two hours. During this time, you will have time to make all the necessary entries on the register. Then the DNS will be updated, but both the old and the new site will be available. So usually the site is not in danger. But there may be short-term glitches with individual providers

V

Vitaly Karasik, 2020-08-02
@vitaly_il1

If you add DNS records to reg.ru in advance, and only then change the servers, then the site will be available all the time .

V

Viktor Taran, 2020-08-03
@shambler81

if you have an A record on the old one that is relevant for the site,
then everything will work fine.
If it’s completely seamless, then transfer another ssl certificates manually (even if it’s Letsencrypt) after everything moves and the cache is reset, then regenerate them already on the current server.

A

Alexey Dmitriev, 2020-08-03
@SignFinder

When transferring a site to another host, there are the following options to avoid failures and downtime.
1. Keep two copies of the site in the old and new locations (you can use a shared database) until the DNS change takes place and plus a margin for updating the client's local DNS server cache.
2. Move the site to a new location, and leave some kind of reverse proxy on the old one, which will proxy requests to the site to the IP address of the new location. Then start changing DNS.
3. Raise the Load Balancer in the third location, transfer DNS to it, and then move - as you please.