How can I install WordPress and make it work on the subdomain example.site.com that is hosted by spaceweb? Even though I have installed WordPress, when I visit example.site.com, I get an error 404. The technical support team confirmed that WordPress is running smoothly on the domain example.site.com.swtest.com, but for the subdomain example.site.com, there is a CNAME record pointing to the main domain site.com instead of the A-record with the subdomain's IP address. I have tried adding CNAME records for example.site.com and www.example, but none of this helps.

So my question is: If site.com is built on a constructor, can I delegate domain rights for example.site.com to another hosting? This problem has been bothering me all day, and I would appreciate any help or suggestions you may have.

If the IP address of a site changes, the A-record must be adjusted accordingly, unless the DNS servers of the hosting provider are used. In this case, the correction of A-records should happen automatically, but it is important to double-check. It's best to consult with a specific registrar for guidance.

If a domain has been delegated to a hosting provider's DNS servers in the registrar panel, NS records for subdomains should be registered in the panel of the hosting provider. If the hosting provider does not allow for this, one option is to use the registrar's DNS servers instead of delegating the domain to the hosting provider's DNS servers. This allows regular records to be registered for the domain directly in the registrar panel, along with regular or NS records for subdomains.

In case the hosting provider's panel does not support third-level domains, creating corresponding 2nd-level domains (dummy) can help. From there, 3rd-level domains as subdomains of 2nd-level domain names can be established. It's important to carefully follow these steps to ensure proper domain management.

One solution for managing multiple subdomains is to use a record with a group symbol for the site with the most subdomains and individual records for supplementary web sites. DNS hosting can be found in "Mail for Domain" (pdd).

Alternatively, consider using a web hosting service that offers a built-in DNS manager, such as cPanel, which avoids these issues.

Adding a dummy second-level domain does not make sense to add again on another site since it was already added as a regular second-level domain. Unfortunately, many hosting services are still focused on level 2 domains, which can lead to problems when trying to distribute subdomains of the same level 2 domain to different sites.

It's worth considering why there is a need for numerous subdomains attached to different sites before taking any action.

The location of domains and their registrar does not matter in general. One registrar can manage a domain serviced by Google DNS hosting or hurricane electric dns, for example.

Regarding your situation, two records need to be created in domain management with the IP addresses of the machines that will serve your site. These machines must be capable of accepting and processing requests.

As an interesting side note, try pinging localhost.icce.im.

To adjust the A-record when the site's IP address changes, it must be done independently unless you use the hosting provider's DNS servers. In this case, the correction of the A-records should happen automatically, but it is important to double-check. If there are any issues, it's best to consult with a specific registrar.

If the domain has been delegated to the DNS servers of the hosting provider in the registrar panel, NS records for subdomains should be registered in the panel of the hosting provider. If the hosting provider does not allow for this, one option is to use the registrar's DNS servers instead of delegating the domain to the hosting provider's DNS servers. This allows regular records to be registered for the domain directly in the registrar panel, along with regular or NS records for subdomains.

In case the hosting provider's panel does not support third-level domains, creating corresponding 2nd-level domains (dummy) can help. From there, 3rd-level domains as subdomains of 2nd-level domain names can be established. It's essential to carefully follow these steps to ensure proper domain management.

To install WordPress on the subdomain example.site.com hosted by Spaceweb, you can follow these steps:

1. First, make sure you have WordPress properly installed on your server. You mentioned that WordPress is running smoothly on the domain example.site.com.swtest.com, so you should double-check that everything is set up correctly there.

2. Next, login to your hosting account at Spaceweb and navigate to the DNS management section.

3. Look for the DNS settings related to your subdomain example.site.com. It seems that currently, there is a CNAME record pointing to the main domain site.com instead of an A-record with the subdomain's IP address. To resolve this issue, you need to update the DNS settings.

4. Remove any existing CNAME records for example.site.com and www.example.

5. Add a new A-record for the subdomain example.site.com, pointing it to the IP address of your hosting server where WordPress is installed.

6. Save the changes and wait for the DNS changes to propagate. It may take some time for the changes to take effect, so be patient. This propagation process can take up to 24 hours in some cases.

By following these steps, you should be able to resolve the 404 error and access your WordPress site on the subdomain example.site.com. If you continue to experience issues or need additional assistance, it would be best to reach out to Spaceweb's technical support team for further guidance specific to their setup.


If your main domain site.com is built using a website builder or constructor and you want to delegate domain rights for the subdomain example.site.com to another hosting provider, you may need to make some changes. Here are some steps you can take:

1. Check if your website builder allows you to delegate subdomains to other hosting providers. Some website builders have this feature, while others may not. Consult the dоcumentation or support resources provided by your website builder to see if this is an option.

2. If your website builder does not support delegating subdomains, you can consider the following alternative solution:

  a. Set up a reverse proxy: In this setup, you would keep the main website on the website builder platform and configure the subdomain example.site.com to act as a reverse proxy. The reverse proxy will forward requests made to example.site.com to your new hosting provider where WordPress is installed. This way, visitors accessing example.site.com will see content from your WordPress installation, even though the main website is hosted on a different platform.

3. To set up a reverse proxy, you would need to configure the DNS settings for the subdomain example.site.com to point to the IP address of your new hosting provider. This can usually be done by creating an A-record in your Spaceweb's DNS management panel.

4. Additionally, you would need to set up the reverse proxy configuration on your new hosting provider. The specific steps for this will depend on the hosting provider you choose and the server configuration they offer. You might need to consult their dоcumentation or contact their support for assistance with setting up the reverse proxy.

5. Keep in mind that setting up a reverse proxy can be more technically involved and may require advanced knowledge. If you're not comfortable with this approach, it's recommended to seek assistance from either Spaceweb's support or a third-party expert who can guide you through the process.