Implementation of domain parking functionality is necessary. The approach described below is based on assumptions, so alternative methods are welcome.

Initially, the domain's CNAME should be associated with a particular site (park.example.ru), where the script is operational. Once the user's desired destination has been determined, the appropriate page is presented to them by substituting it there.

As for binding a CNAME to your server, using a server management system like VestaCP might do the trick. However, I am not entirely sure how this works.

Once that is sorted out, a PHP script needs to be written to load the correct page. Although the specifics of the script's operation are still unclear, I am open to suggestions on how best to approach this task.

CNAME functions as an alias and requires a corresponding "A" entry specifying the IP address of the domain. Vesta offers a built-in DNS server, and for hosted sites, you need to specify the NS servers of your server, like "NS1.YOUR_SERVER.com." The server's DNS record itself cannot work on itself, so delegating the domain to a third-party service is necessary.
To create records of the type Your site.com-A 1.1.1.1, www.-A 1.1.1.1, NS1-A 1.1.1.1, NS2-A 2.2.2.2 (if no second IP, use the first), etc., find out if your registrar has free or paid parking with DNS zone editing. No php is needed; Apache breeds sites depending on the HTTP header when requesting and substitutes the required folder. A web server can harbor hundreds of sites on one IP and port.

Binding all CNAMEs to yourself is unnecessary; instead, linking one site to an IP will open any sites with that IP as an alias. Make sure nginx/apache is not restricted by server_name.
To bind domains to IP, there are two options: owners can register CNAME/A for their domains, or they can delegate the domain to your DNS servers, which will then provide the necessary CNAME/A records.
When a script exists on your server, it detects the HTTP HOST header to determine the domain name and its content to display.

One possible reason for an advertising campaign rejection is a domain with a poor history that has been previously blocked. By placing a landing page on your domain, you avoid this issue, as you have control over it and do not need your own server.
Domain parking assumes greater relevance with authorized products/services like physical goods, training, online stores, finance, etc. However, if you have to edit the landing page or enable lead transfer via the API, then owning a hosting or server is necessary.
Parking your domain affords security for your advertising campaigns, as your partner domains are not visible during the referral link creation process where advertising creatives are monitored.
Finally, you can select a pertinent domain name for the product/service advertised.

The approach to domain parking can vary based on the specific requirements of the project, and alternative methods can also be explored to achieve the desired outcome.

To begin with, associating the domain's CNAME with a specific site, such as park.example.com, can be accomplished by accessing the domain management system provided by the registrar or utilizing a server management system like VestaCP. In the case of VestaCP, the process generally involves adding the domain as an alias to the existing web hosting account, and then configuring the CNAME record to point to the desired site for parking.

Once the CNAME association is established, the next step is to create a PHP script that will dynamically load the correct page based on the user's desired destination. This script can utilize server-side programming to analyze the user's input and serve the appropriate content accordingly. The specifics of the script's operation might involve parsing the requested domain, matching it with predefined destinations, and forwarding the user to the corresponding page seamlessly.

When it comes to writing the PHP script, it's crucial to consider security measures to prevent potential vulnerabilities, such as validating user input and ensuring proper handling of redirects. Additionally, the script's performance and efficiency should be optimized to provide a seamless experience for the end users.
The implementation of domain parking functionality involves associating the domain's CNAME, configuring a server-side script to handle user requests, and ensuring the overall security and performance of the solution. Collaboration with domain parking specialists, web developers, and server administrators can provide valuable insights and alternative methods for achieving the desired functionality.