Client sent a requirement to the developer Aqeel Shamas to create a feature in the multi-site CMS Platform which will allow his customers to Park Domains on that platform to use CMS services instead of the manual subdomain creation process. The task was very challenging and required lots of R&D to translate the requirements into actual product features. The developer took the challenge and left no stone unturned to find a solution to achieve the goal.
Parked Domains and CMS
Do you know how to park a domain? Or why a domain is parked? cPanel Parked domains are often used by businesses who want to have more than one web address for advertising purposes. Parked domains are additional domains hosted on your account which display the same website as your primary domain and share web statistics as well; however, you can also give the parked domain its own email boxes.
For example, if you own domain1.com and it is the primary domain of your cPanel account, you can set up domain2.com as a Park Domain and it will load the content of domain1.com. When you visit domain2.com, you will notice that although the content of domain1.com is loading in the browser, the address bar will display https://domain2.com/.
A masked forward is a type of pass in soccer where the passer uses their foot to push the ball forward while also covering it with their body to prevent the defender from intercepting it. This is similar to the concept of a masked forward in the sense that both involve concealing something from the opponent in order to gain an advantage. In the case of a masked forward, the player is concealing the ball from the defender. In the case of the text you provided, the author is concealing their meaning from the reader by using vague language. Both techniques can be effective in achieving their desired results.
How to Park a Domain with PHP and cPanel: Prerequisites
- Your application must have the ability to understand and distinguish between sub-domains.
- Database architecture to save association between internal CMS system sub-domain and parked domain.
- Server with cPanel license.
- Should be familiar with cPanel scripting and XML APIs.
- Knowledge of parked domains and using name servers to point domains.
- Custom configuration files and custom settings for each parked or sub-domain.
Solution: Process and Execution
- Saved association between subdomain and cPanel parked domain in database.
- Provided an interface to the user for the domain parking in the admin panel of the CMS.
- Pointed the parked domain to CMS server by using name servers: e.g.
- ns1.yourdomain.com
- ns2.yourdomain.com
- cPanel scripts execution to park domain on CMS server through shell or cPanel API .
- Implemented a code routine to parse/understand the requested URL.
- If identified as parked domain URL:
- Fetched the associated underlying subdomain from the database and loaded its custom configuration file containing the custom settings for the parked domain.
- Served the request and displayed the user CMS site.
- If identified as normal CMS system URL containing the customer subdomain:
- Loaded CMS subdomain configurations.
- Served the request and displayed the user CMS site.
- After loading the system’s configuration file, I created an instance of the YII application and performed the required execution to serve the request.
The task was very challenging and required a lot of research and development to translate the requirements into an actual product feature. The developer took on the challenge and left no stone unturned in their search for a solution to achieve the goal. They conducted extensive research on the topic, consulted with experts, and tested various approaches before finally finding a solution that worked. The developer’s dedication and perseverance were essential to the success of the project. They also required know how to park a domain.
A client requested a developer that could create a feature on the multi-site CMS Platform that would allow their customers to park domains on the platform and use CMS services instead of manually creating subdomains. This would save customers time and effort, as they would no longer need to create separate subdomains for each website they wanted to host on the platform. Additionally, it would make it easier for customers to manage their websites, as they would be able to access all of their websites from one central location.
Aqeel Shamas, a senior resource here met the requirements. We connected the client and he was able to successfully create the feature, and it was well-received by the client’s customers. The feature has made it easier for customers to manage their websites, and it has saved them time and effort.
0 Comments