If you like DNray Forum, you can support it by - BTC: bc1qppjcl3c2cyjazy6lepmrv3fh6ke9mxs7zpfky0 , TRC20 and more...

 

Moving a Website from Shared Hosting

Started by prulseerurnox, Jul 27, 2023, 07:09 AM

Previous topic - Next topic

prulseerurnoxTopic starter

There are two shared hosting servers available. One of these servers is currently hosting a website, along with several other sites that are hanging on subdomains.
The main concern is how to transfer the website from its current server (www) to a new server, while ensuring that the sites on the subdomains continue to function properly on the old hosting.
  •  


seanmarshall

To transfer the website from the current server to a new server while ensuring the subdomains continue to function properly on the old hosting, you can follow these steps:

1. Set up the new server: Start by setting up the new server with the necessary software and configurations. Ensure that it meets the requirements of your website.

2. Transfer the website files: Copy all the website files from the current server to the new server. This can be done using FTP or through a file manager provided by your hosting provider.

3. Export the website database: Export the database associated with the website from the current server. This can usually be done through a database management tool like phpMyAdmin.

4. Import the database on the new server: Create a new database on the new server and import the exported database from the previous step.

5. Update configuration files: Update any configuration files on the new server to reflect the new database connection details and other relevant settings.

6. Test the website on the new server: Once the website is transferred, test it thoroughly on the new server to ensure it is functioning correctly. Make sure all links, images, and functionalities are working as expected.

7. Update DNS records: Once you are satisfied with the testing on the new server, update the DNS records for the main domain to point to the IP address of the new server. This will make the main website accessible from the new server.

8. Verify subdomain functionality: After updating the DNS records, confirm that the subdomains and their respective sites are still functional on the old server. You can do this by accessing the subdomains' URLs and checking if they load properly.

By following these steps, you can safely transfer the website to a new server while ensuring the subdomains continue to function without interruption on the old hosting.


Here are a few additional considerations and tips for transferring the website and managing the subdomains during the process:

1. Backup everything: Before starting the transfer process, it is crucial to create backups of all website files, databases, and configuration settings on both the current server and the new server. This ensures that you have a safety net in case anything goes wrong during the transfer.

2. Communicate with your hosting provider: If you are migrating to a new hosting provider, it's important to notify them about your plans and seek their assistance if needed. They might be able to provide guidance or perform the transfer for you.

3. Configure the subdomains on the new server: Set up the necessary subdomains on the new server to match the ones on the old server. This includes creating the required directories and setting up DNS records for each subdomain.

4. Modify DNS settings selectively: Instead of updating all DNS records at once, consider updating only the main domain's DNS records initially. This way, the main website will be accessible from the new server, while the subdomains continue to function on the old hosting. Later, when you're ready, update the DNS records for the subdomains to point to the new server.

5. Monitor DNS propagation: Keep in mind that it may take some time for DNS changes to propagate fully. During this period, some users might still see the old website while others see the new one. It's advisable to monitor the DNS propagation progress and notify your users or visitors about any potential downtime or intermittent access during this period.

6. Test subdomain functionality on the new server: Once the main website is successfully transferred to the new server, you can verify that the subdomains work correctly by accessing them via the new server's IP address. This allows you to confirm that the subdomains' websites are functioning properly before updating their DNS records.

7. Update subdomain DNS records: After testing the subdomains on the new server, update their DNS records to point to the IP address of the new server. This ensures that the subdomain websites are served from the new hosting.

8. Monitor and troubleshoot: After completing the transfer, closely monitor both the main website and the subdomains to identify any issues or inconsistencies. Make sure all functionalities, forms, and databases work as expected. If you encounter any problems, review your configurations and seek support from your hosting provider if needed.
  •  

MuhammadHaseeb

Get in touch with experts who can handle the task efficiently in exchange for compensation.

The main issue at hand involves 1) relocating the website and 2) resolving a DNS entry problem.
  •  

NamanModi

Duplicate the website and its database, transfer the domain to regular nameservers (using ispmanager muzzle, regrush, or their partners), and configure DNS resolution. In essence, handle all of these tasks.

ensure that all aspects of the website, including its content and functionality, are accurately replicated. Additionally, proper domain delegation and DNS resolution are key to maintaining a smooth online presence.
  •  

siyajoshi

To begin, I would thoroughly analyze the current server setup and take note of all the specific configurations and dependencies related to the main website. This includes examining the web server, database management system, and any other software crucial for the site's operation.

Following this, I would set up the new hosting server to replicate the configuration of the existing server, ensuring that it can support the main website effectively. This involves installing the necessary software, configuring the server operating system, and verifying compatibility with the website's codebase.

Next, I would perform a comprehensive backup of the main website's files, databases, and any associated scripts or configuration files. This step is essential to safeguard against any potential data loss and to provide a restore point in case of unforeseen issues during the migration.

I would develop a detailed communication plan to keep stakeholders informed about the upcoming migration. This would involve creating notifications for website visitors, FAQs to address common concerns, and establishing clear support channels for addressing any issues that may arise during the transition.

Throughout this process, I would also strategize ways to maintain the online presence of the main website during the migration period, leveraging various channels such as social media and email to redirect traffic and provide updates to users.
  •  


If you like DNray forum, you can support it by - BTC: bc1qppjcl3c2cyjazy6lepmrv3fh6ke9mxs7zpfky0 , TRC20 and more...