To get your WordPress website ready for production, a custom domain should be added and bound. This will allow you to access your website using a domain name of your choice rather than the default domain provided by the platform.
Let’s assume you have a WordPress application with clusterization across all stack layers. It means that the cluster has two LiteSpeed Web ADC (load balancers), which serve as the entry points (origins or endpoints).
1. Before you can use a custom domain name for your WordPress application, you need to purchase it at any preferred domain registrar. Refer to the Choose Domain Name section of the All-in-One Guide for some tips on how to choose a domain name.
2. After that, you can bind it to your WordPress application by creating DNS records. At the domain registrar, create an A record for each endpoint that points to a custom domain name, for example wordpress-enterprise.jele.website.
Notes:
- If using a standalone WordPress package, you need just one A record pointing to the public IP address of the LLSMP/LEMP container with your WordPress application.
- If you are going to scale load balancers horizontally, register each newly provisioned public IP address under the same custom domain name as one more A record.
- If using a multi-region WordPress installation, you need to add A records for each entry point in each region.
3. Issue an SSL certificate for the custom domain name. Go to the Add-Ons tab for the load balancer’s layer of your WordPress cluster and find the Let’s Encrypt Free SSL add-on.
4. Click on the Configure button to open the configuration window and replace the platform-generated domain name with your custom one. Press Apply to issue a valid SSL certificate.
5. Next, you need to update the URL for your WordPress site, which can be done with the dedicated WordPress Site Address (URL) add-on at the application server layer of your WordPress cluster.
6. Click on the Site URL button and enter the new domain name.
The add-on will automatically update the WordPress configuration file and database with the new URL.
7. At this point, your site is served via the DNS Round-Robin algorithm. If you try to resolve the domain name, you’ll get all the addresses you have registered for it every time (even the unreachable ones).
From now on, you should use the custom domain to access the WordPress website and admin panel. If you have multiple entry points to your WordPress application, consider setting up DNS load balancing to ensure traffic is routed only to healthy endpoints.
