Changing host and Registrar without a downtime, is that even

Changing host and Registrar without a downtime, is that even possible?
So, I currently have one site which is hosted by registrar itself. And I want to change it to a separate host and registrar.

++++++++++++++
list of top cheapest host http://Listfreetop.pw

Top 200 best traffic exchange sites http://Listfreetop.pw/surf

free link exchange sites list http://Listfreetop.pw/links
list of top ptc sites
list of top ptp sites
Listfreetop.pw
Listfreetop.pw
+++++++++++++++

Is there any way so I can avoid downtime of my site? Or, you know do it in way so my site has to face the least amount of downtime.
Is the site a static site?

If yes, transfer files over then once files are transferred update nameservers on the domain.

If no (people login to the site ect) then there will be slight downtime as you transfer the databases ect and updated pages over.
█ Dan Simmon, HBHosting.com.au
Is the site a static site?

If yes, transfer files over then once files are transferred update nameservers on the domain.

If no (people login to the site ect) then there will be slight downtime as you transfer the databases ect and updated pages over.
Its a small forum. Sunday are low. So, I am thinking maybe on Sunday it should be done. Can you tell me the processes? What to be done in a step by step manner? Should I go for transferring files to new host or change the registrar first?
Here's to do it with only a couple of minutes of downtime:

1. Copy (a snapshot of) all files and database contents to the new server. Exactly how you do this depends on which CMS and control panels you are using - follow their guides. You can copy email users across as well. It's a good opportunity to test your whole backup and restore process.

2. Add entries to your hosts files on the server and on your PC so that they think the DNS points to the new server. Test that everything looks the same and works properly.

3. If you want to keep files and emails up to date throughout the DNS change, set up rsync on a cron job to do this. You will require an SSL connection using key authentication so it can run unattended. If files are unlikely to change for a day or two and you're not worried about emails you can skip this step.

4. To keep database contents in sync, change the CMS settings on the new server so it actually points to the database on the old server temporarily. You may need to change the database configuration and the old server and open port 3306 in the firewall to allow this. Now test that everything still looks the same and works properly on the new server, including latest emails and updates.

5. Now switch the DNS settings. It shouldn't matter if people connect to the old server or new server or if emails and orders arrive at the old server or new server because the contents are in sync.

6. Wait a couple of days for DNS changes to fully propagate around the world. Remove the extra lines in your hosts files. Disable the rsync jobs. Put the site into maintenance mode and take one final copy of the database contents and do one final rsync (this is the bit where you need a "couple of minutes" of downtime). Switch the config file to point to the new database. Take the site out of maintenance mode.

It's not a completely foolproof process (emails and images may temporarily vanish or revert to an old version as the DNS switches or between cron runs) but it's good enough for most sites.
Last edited by Phil McKerracher; 05-28-2019 at 01:17 PM.
Phil McKerracher
www.beeches.it
Not a hosting company, but I fix hosting problems
Re-reading your original post, if all you want to do is change the registrar but the site stays at the original hosting then it's a much simpler process. You simply initiate a domain transfer, again following the specific instructions at the orignal and new registrar, and most registrars will automatically copy the DNS settings. In that case there should be no downtime at all.

linkshar.eu
liberainformazionenews.it
bubblews.com
247ptp.com
domain 3d danielson
how can l make money
go.cur.lv
trafficmarketplace.org
host 0 boot from backup root
cut-win.com

Note however that if you make changes in your control panel that affect DNS settings (such as adding a subdomain or updating DKIM) then those DNS updates will probably no longer be automatic if they were previously. It's easy enough to copy them manually though. Personally I use Cloudflare for my nameservers anyway.
Phil McKerracher
www.beeches.it
Not a hosting company, but I fix hosting problems
Good and detailed explanation by Phil.

Alternate method I've used for a forum was with Cloudflare (and their DNS, of course). Change gets propagated practically instantly from what I could tell.

Large database import was the biggest challenge for me - there's a topic here that deals with solutions, but I understand linking to it would be against forum rules.
Mostly harmless?
Changing both the registrar and hosting without a downtime, can be tricky, but possible. Apart from what said above, you can also try the following novice guide:

1. Transfer the domain first. When completed, the domain will still use the nameservers of your old host (in your case, old registrar since you are using their hosting).
2. On your new hosting modify all the DNS records. Change the IP address to that of your old hosting, lower the TTL value to 300 (5 minutes).
3. Change the nameservers with the ones pointing to your new hosting. Since the DNS records on your new hosting resolve the old hosting IP, your website will still be live.
4. Lower the TTL value of the DNS records on your old hosting to 300.
5. Wait 72 hours for the DNS propagation.
6. Migrate your site from old server to new.
7. Modify the DNS records on the new server to make sure they are resolving the new server's IP.
8. Modify the DNS records on the old server to make sure they are resolving the new server's IP.

The DNS propagation should be completed within 5 minutes since you have lowered the TTL values. Any email might still arrive at the old server within that 5 minute.
...The DNS propagation should be completed within 5 minutes since you have lowered the TTL values. Any email might still arrive at the old server within that 5 minute.
Be careful with this. The DNS change might appear to be quick to you, but someone sending mail messages might not see the change for hours. The reason is, many DNS servers ignore TTL settings shorter than an hour, to save CPU and bandwidth (which is expensive in some places). And the change might have to go through several servers.

The good news is, you don't necessarily have to synchronise mail messages between servers - you can simply switch off the old mail server, and most genuine mail clients will keep trying to send messages until the DNS change reaches them and they can contact the new server. So messages might be delayed but they're unlikely to be lost completely.
Phil McKerracher
www.beeches.it
Not a hosting company, but I fix hosting problems
Re-reading your original post, if all you want to do is change the registrar but the site stays at the original hosting then it's a much simpler process. You simply initiate a domain transfer, again following the specific instructions at the orignal and new registrar, and most registrars will automatically copy the DNS settings. In that case there should be no downtime at all.

Note however that if you make changes in your control panel that affect DNS settings (such as adding a subdomain or updating DKIM) then those DNS updates will probably no longer be automatic if they were previously. It's easy enough to copy them manually though. Personally I use Cloudflare for my nameservers anyway.
So, my choice is ********. So, will it be okay that I change my registrar first and then go for changing the hosting?
So, will it be okay that I change my registrar first and then go for changing the hosting?
Doesn't matter whichever comes first
To state the obvious, just in case:

Whichever approach you take, you'll probably be doing the migration at a low traffic time - which is often not 11 am.
Write down every step you make, as you make it. It will help figure out any mistakes made and, at least for me, it helps one think more clearly: it's hard not knowing exactly what one is doing, even if sleepy, when taking the time and making the effort of writing each step down in a way that can be referenced at a later time.
Mostly harmless?
Be careful with this. The DNS change might appear to be quick to you, but someone sending mail messages might not see the change for hours. The reason is, many DNS servers ignore TTL settings shorter than an hour, to save CPU and bandwidth (which is expensive in some places). And the change might have to go through several servers.
Valid point. But haven't experienced something similar in a long time. The last time we've seen an ISP ignoring the TTL is about 6 years ago in a developing country.
█||||[ Fully Managed ][ Shared, Reseller, Dedicated Server Hosting ][ cPanel | CloudLinux | LiteSpeed ]
So, my choice is ********. So, will it be okay that I change my registrar first and then go for changing the hosting?
You can change your registrar (or your nameservers, which may be at a different supplier like Cloudflare) any time you like as long as the DNS records (A, AAAA, MX etc.) are the same. They may be copied automatically but you should definitely check them.

If you change the IP address in the DNS records then obviously you need to make sure the new site is ready at the new address first.
Phil McKerracher
www.beeches.it
Not a hosting company, but I fix hosting problems
You can change your registrar (or your nameservers, which may be at a different supplier like Cloudflare) any time you like as long as the DNS records (A, AAAA, MX etc.) are the same. They may be copied automatically but you should definitely check them.

If you change the IP address in the DNS records then obviously you need to make sure the new site is ready at the new address first.
Alright got it.