If you’re looking to create a custom domain with WordPress but don’t want to install WordPress, you can use the “Web Site Migration” feature to migrate your WordPress site to Plesk. You can also use the Image Gallery module to create a custom subdomain. You can even use Amazon Route 53 as a DNS server. This article will show you how to do all of these tasks with Plesk.
Contents
Using the “Web Site Migration” feature to migrate WordPress sites to Plesk
If you are planning to migrate WordPress sites to Plesk, you may have several reasons. Some of them are related to unhappy clients who want to switch to a different hosting company. Below are some tips for migration. Identify the prerequisites of your site. By identifying these prerequisites, our engineers can deploy a system that is capable of running the service. In addition, FTP migrations may result in lost functionality or custom permissions. Migrations via Plesk, however, ensure that all settings will be carried over.
To begin migrating WordPress websites to Plesk, go to Websites & Domains > WordPress and click “Import.” Next, follow the instructions to import your WordPress site. During the migration, Plesk will automatically make a backup copy of your site’s files and database. Afterward, you can manage the migrated WordPress website with the WordPress Toolkit.
To migrate a WordPress site to Plesk, you can use a free plugin called “WP Toolkit” to copy selected data between the two websites. It also makes a copy of files and database tables between the source and target sites. You can also choose to copy only the files. However, you should be careful not to delete the original files on the target website.
Creating a subdomain without wordpress
Creating a subdomain without WordPress is easy! If you already have a domain name, all you need to do is create a subdomain for it. Creating a subdomain with WordPress is generally free. There are a few steps that you should follow to create a subdomain. After creating the subdomain, you need to configure the database. You can then add or remove users for your subdomain.
First, add the subdomain’s A record. This is called a root record. Basically, an A record points to the IP address of your website, and you need to specify the alias of the domain. After doing this, you need to log into the hosting provider’s control panel and follow the instructions there. You can then start adding websites to your subdomain. This is easy and quick!
Create a subdomain with WordPress. Plesk will automatically complete the Document root and Preferred domain fields. The Document root is the directory where your website files are stored. You should also select Preferred domain to redirect the site, which is usually used for SEO purposes. Afterward, click Add and select a new domain and subdomain. After that, click Finish to save the settings. Once the website is live, you can access your files and edit them as needed.
Image Gallery module
Having a Plesk Image Gallery module for subdomain websites without WordPress allows webmasters to add an image gallery to their sites. Having an image gallery is not a problem if you’re hosting a WordPress site, but what if you’re hosting a subdomain without WordPress? It can be a hassle to figure out where to add the images, but the good news is that Plesk provides a plugin to do the job.
Using Amazon Route 53 as a DNS server
One way to use AWS Route53 as a DNS server to display images in a subdomain without a WordPress installation is to register a domain name with it. Registering the domain with AWS Route 53 or any other domain registrar will allow you to route internet traffic to the appropriate servers. AWS Route 53 also helps with domain name registration and health-checking. It provides a cost-effective approach to routing end-user requests to applications. It derives its name from Port 53, which is used for TCP and UDP traffic. However, Route 53 may also refer to the popular highway naming convention used in the United States.
Once you have your domain registered with AWS, you can import your domain’s zone file to use AWS Route 53 as a DNS server. To do this, simply login to your domain’s service and change the value of the name servers to the AWS values. Then, your Route 53 will take care of domain and subdomain routing. Once you’ve configured your DNS server, you’ll need to request a public SSL certificate. This process is quick and easy. You must be in the same region as your EC2 instance. Click on the button “Request a certificate” to request your public certificate.
Using Amazon Route53 as a DNS server allows you to manage your domain’s DNS settings from the Plesk admin interface. The DNS server also acts as the primary (master) DNS server and propagates changes to external servers. It is important to remember that you’ll need to update your DNS if you’re moving from one hosting service to another.
A DNS cache can affect your website’s performance, but the use of Amazon Route 53 as a DNS server can solve this problem. If you use Route53 to host your website, you’ll have to update your nameservers to point to Cloudflare. It can take up to 48 hours before the changes take effect. If you don’t want to wait that long, you can always use a free trial of Cloudflare.