Connecting an external domain to CURIAWEB hosting

A domain and a hosting package are technically two separate things. The domain is the name visitors enter in the browser, such as yourdomain.ch. Hosting is the server space where your website files, databases and, depending on your setup, email services are located.

If your domain is registered with an external provider, it can still be connected to CURIAWEB hosting. The key is that the DNS settings are correct and that the domain is also added to your cPanel account. Only when both sides are configured correctly can the website work reliably.

Which Connection Method Is Right?

There are two clean ways to connect an external domain to your CURIAWEB hosting. The better option depends on whether you want to move the entire DNS management to CURIAWEB or whether specific services should remain with the previous provider.

Option A: Change Nameservers – Recommended Method

Changing the nameservers is often the cleanest and easiest method. You tell the domain registrar that the DNS zone for your domain should be managed through CURIAWEB nameservers going forward.

After the change, DNS records such as A records, CNAME, MX, TXT, SPF, DKIM or DMARC can be managed directly in cPanel or through the related cPanel functions. This is especially convenient if website, email and DNS should be handled centrally by CURIAWEB.

Enter the following nameservers at your external domain provider:

Step by Step: Change Nameservers at the External Provider

1. Log in to your domain provider’s customer area.
2. Open the management page for the relevant domain.
3. Find the section called Nameservers, DNS servers or Delegation.
4. Replace the existing nameservers with ns1.curiaweb.ch and ns2.curiaweb.ch.
5. Save the change.
6. Wait for DNS propagation. Depending on the registrar, registry and DNS cache, this may take some time.
7. Afterwards, check in CURIAWEB cPanel that the domain has been created correctly.

Important Note About Existing Email

Changing the nameservers affects not only the website but the entire DNS zone. This includes mail server entries, known as MX records, as well as TXT records for SPF, DKIM or DMARC.

If your email currently runs through an external provider such as Microsoft 365, Google Workspace or your previous provider, the relevant DNS records must also be added correctly in CURIAWEB cPanel after the nameserver change. Otherwise, email delivery or sending may be affected.

Option B: Point Only the A Record to CURIAWEB

The A record method is useful if DNS management should remain with the current provider and only the website should run through CURIAWEB. In this case, you change the A record of the domain at the external DNS provider to the IP address of your CURIAWEB server.

This method is often used when email, newsletter systems, verifications or other DNS-dependent services should continue to be managed externally.

Step by Step: Change A Record at the External DNS Provider

1. Log in to the provider that manages the DNS zone for your domain.
2. Open the DNS management area for the domain.
3. Find the A record for the main domain, often shown as @, yourdomain.ch or an empty hostname.
4. Change the target value to the IP address of your CURIAWEB server.
5. Also check the entry for www. This is often a CNAME pointing to the main domain or a separate A record.
6. If an AAAA record exists, check whether it is still correct. An incorrect AAAA record can send visitors to the wrong destination via IPv6.
7. Save the changes.
8. Wait for DNS propagation and then test the domain.

Add the Domain in cPanel as Well

Regardless of whether you change the nameservers or only set the A record: the domain must be added to the cPanel account so the web server knows which website should be served for that domain.

Step by Step: Add the External Domain in cPanel

1. Log in to your CURIAWEB cPanel.
2. Open the Domains section.
3. Click Create A New Domain.
4. Enter the full external domain, for example yourdomain.ch.
5. If the domain should display its own website, disable Share document root with the main domain.
6. Check the suggested document root or enter a suitable folder.
7. Save the domain.
8. Upload the website files to the document root or install your CMS there.

If the domain should only display the same content as your main domain, the document root can be shared. If it should have its own website, use a separate document root.

DNS Propagation and Waiting Time

DNS changes are not always visible worldwide immediately. Many resolvers, providers and devices cache DNS responses for a certain time. It is therefore possible that the domain already works for you while other visitors still see the old server.

Changes are often visible within minutes to hours. Depending on TTL, registrar, registry and DNS cache, it may take longer. During this period, avoid making repeated uncontrolled changes to old DNS settings. Wait for propagation and verify carefully.

SSL Certificate and HTTPS After Connection

Once the domain correctly points to CURIAWEB hosting and has been added in cPanel, an SSL certificate should be available for the domain. Depending on the hosting configuration, AutoSSL may issue a certificate automatically once the domain is reachable.

Only enable HTTPS redirection after a valid certificate exists. Otherwise, visitors may see browser security warnings.

Which Method Should You Choose?

Choose the nameserver method if you want to manage your domain as simply and centrally as possible through CURIAWEB. This option is especially suitable if website, DNS and possibly email should run through CURIAWEB.

Choose the A record method if you only want to move the website to CURIAWEB while email, DNS management or other services remain with the current provider.

Common Mistakes and How to Avoid Them

1. Domain points to CURIAWEB via DNS but is not added in cPanel

In this case, the domain may reach the server, but the web server does not know which document root belongs to that domain. Add the domain in cPanel under Domains.

2. Nameservers changed but old mail records not copied

If external email services are used, MX and TXT records must be present correctly in the new DNS zone after the nameserver change.

3. Main domain changed but www forgotten

Always check www.yourdomain.ch as well. This version should either point to the main domain via CNAME or be configured with a suitable A record.

4. Incorrect AAAA record exists

If an outdated IPv6 record exists, some visitors may reach the wrong destination via IPv6. Remove or correct the AAAA record only if you know which IPv6 configuration is required.

5. HTTPS enabled too early

Forced HTTPS redirection should only be enabled once the SSL certificate is valid. Otherwise, browser warnings may occur.

Frequently Asked Questions About Connecting an External Domain

Do I have to transfer my domain to CURIAWEB?
No. You can keep the domain with the current provider and still connect it to CURIAWEB hosting. A transfer is optional.

Which option is better: nameservers or A record?
If CURIAWEB should manage DNS, nameservers are usually the better choice. If only the website should move while email remains external, the A record method is often more suitable.

Will my emails remain active?
That depends on the DNS configuration. If mail services remain external, MX and TXT records must be preserved or copied to the new DNS zone correctly.

Why does the domain not work after the change?
Possible causes include DNS propagation, incorrect nameservers, a wrong A record, a missing cPanel domain entry or an SSL certificate that has not yet been issued.

Can CURIAWEB check the DNS settings?
Yes, CURIAWEB Support can help review them. For external registrars or DNS providers, screenshots or access to the DNS settings may be required.