P
P
photosho2019-12-12 16:57:22
Domain Name System
photosho, 2019-12-12 16:57:22

Is it possible to minimize site failure time?

When transferring a site from one hosting to another, NS-records are changed from 8 to 24 hours. What part of this time is the site down on average (the old one has already stopped working and the new one has not started working yet)? If it is a significant portion of the time, is there any way to minimize it?

Answer the question

In order to leave comments, you need to log in

4 answer(s)
A
Alexey Dmitriev, 2019-12-12
@SignFinder

You can - transfer the site database and set up a copy of the old site to work with the database of the new site.
In this case, changes will be written to one database from both the old and the new copy of the site.
Or, as an option, use a third server that will glow in DNS and proxy all web traffic first to the old server, and then to the new one. After the move, it will be possible to change the DNS record so that it looks at the new server and after a while get rid of this intermediate one.

S
Sergey, 2019-12-12
@feanor7

Everything is usually faster and sometimes depends on the NS servers of the hosts.
My practice shows differences in a couple of hours after uploading a new zone.
In general, it is during the transfer that you do not make changes to our site, well, as a rule, you can leave the old site mirror to work for 2-4 hours, then stop the web server. It all depends on the hosting itself.

D
Dimonchik, 2019-12-12
@dimonchik2013

for "hosting" this is not a problem at all - it will not decrease,
but on servers it is simply solved

A
akelsey, 2019-12-15
@akelsey

I would change the strategy of transferring sites from hosters, use nsky registrars or free ones like cloudflare (it is also not forbidden to use paid ones).
Then you can transfer sites at least every hour (after setting up TTL records)

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question