How to minimise downtime when transferring a domain

Written by Pietro Strada on 27 December 2025. Posted in Blog.

Transferring a domain to a new host with minimal downtime requires careful planning. Here’s the best approach:

1. Choose Your New Hosting Provider & Set It Up

Sign up with the new hosting provider.
Set up your website, including files, databases, email accounts, and any necessary configurations.
Test the new hosting environment using a temporary URL or staging domain. This is hosting provider specific so you should check with them.

2. Lower the TTL (Time-To-Live) on Your DNS Records

In your current DNS settings (likely managed by your domain registrar or old host), lower the TTL value for your domain to 300 seconds (5 minutes).
This ensures that when you update your DNS, changes propagate quickly.
Do this 24-48 hours before switching hosts.

3. Complete the Migration of Your Website Files & Databases

If your current site has had any updates since you set up the site on the new hosting provider make sure that you transfer those updates to the new site.
Export and import your database if applicable.

4. Test the New Host Before Switching DNS

Use a hosts file modification on your local computer to test the new host before changing the domain settings.
192.134.45.678 example.com
Ensure everything works correctly.
Remove the hosts file modification (very important)

5. Update Your Domain’s DNS Records

If you’re keeping the same domain registrar and name servers, update the A record (for website) and MX records (for email) to point to the new host.
If you’re transferring the domain to a new registrar, update the name servers to the new hosting provider.

6. Monitor & Verify

Check that the site is live on the new host.
Use nslookup or dig commands or an online checker to verify DNS propagation.
Keep the old hosting account active for 48-72 hours as a fallback.

7. Raise the TTL Back Up

Once everything is stable, increase the TTL back to a higher value (e.g., 3600 seconds or more) for normal operation.

Some articles published on the Joomla Community Magazine represent the personal opinion or experience of the Author on the specific topic and might not be aligned to the official position of the Joomla Project