The domain site.com is registered on REGRU-RU, with nserver ns1.platformalp.com and ns2.platformalp.com. There is a subdomain example.site.com hosted by spaceweb. How can WordPress be installed on example.site.com and ensure that everything works properly?

I have installed WordPress, but I encountered an error 404 on example.site.com. Technical support informed me that WordPress had been installed correctly on the technical domain example.site.com.swtest.com, but not on the subdomain example.site.com because a CNAME record has been registered directing it to the main domain site.com. Additionally, there was an A-record for the subdomain example.site.com with the IP address 22.222.222.22.

I tried adding a CNAME record for example.site.com and www.example, but this did not fix the problem. WordPress works on the technical domain example.site.com.swtest.com, but not on the required example.site.com.

My most important question is how to delegate domain rights for example.site.com to another hosting if site.com is on the constructor. Is this possible?

I have been trying to resolve this issue all day with no success. This is my first encounter with such a problem.

The location or registrar of domains generally does not matter. In fact, a single registrar can manage a domain that is served by Google DNS hosting or Hurricane Electric DNS.

Regarding your situation, you must create two records in domain management. The first record is for site.com with an IP address of XX.xхx.xхx.185 and the second record is for example.site.com with an IP address of Xx.xхx.xхx.139. The machines must be prepared to accept and process requests.

For the sake of testing, you can ping localhost.icce.im.

If you don't need common users or general information, then three different sites can be placed anywhere without any issues. Subdomains are essentially the same as domains, and your domain is a subdomain of one of the root zones.

To technically set this up, you need to create A (and possibly MX and CNAME) records in your domain zone that contain the corresponding IP addresses of the second hosting for the relevant subdomains. The main domain should be served where you can learn how to do this.

Next, you need to bind your sites to these subdomains on the second hosting. Contact the support service of the second hosting, informing them that the domain is served on an external DNS server.

If there is general data, it's better to host on the same webhosting to avoid complications.

It seems that the problem lies in the DNS configuration and the way the subdomain is set up.
Firstly, it's important to ensure that the DNS records for the subdomain example.site.com are correctly configured. The CNAME record for example.site.com should point to the correct location where WordPress is installed. In this case, it seems like the CNAME record might be directing the subdomain to the main domain site.com instead of the correct location.

The A-record for the subdomain example.site.com with the IP address 22.222.222.22 could potentially conflict with the CNAME record if both are pointing to different locations.

To address this issue, you may need to modify the DNS records for the subdomain example.site.com to ensure that it points to the correct location where WordPress is installed. This might involve removing conflicting DNS records or adjusting them to point to the correct location.

Regarding the delegation of domain rights for example.site.com to another hosting, it is indeed possible even if site.com is built on a website constructor. You can achieve this by updating the nameservers for example.site.com to point to the nameservers provided by the new hosting provider. This will effectively delegate the domain rights for the subdomain to the new hosting, allowing you to host example.site.com on a different platform.
Resolving DNS configuration issues and properly delegating domain rights for the subdomain to another hosting provider should address the issues you are facing with installing WordPress on example.site.com. If you need further assistance, don't hesitate to reach out to your hosting provider's technical support or a professional specializing in DNS management.