Keep domain with another registrar and connect to CURIAWEB Hosting

You can use CURIAWEB hosting without having to transfer your existing domain to CURIAWEB. The domain can continue to be registered and renewed with your current registrar.

So that your domain still points to your CURIAWEB hosting, you just need to set up the DNS configuration accordingly.

There are basically two ways to do this: you use the CURIAWEB Nameserver and you manage the DNS zone via the CURIAWEB infrastructure, or you keep the previous nameservers and only adjust the required DNS records at your previous DNS provider.

Briefly explained: Domain registration and web hosting do not have to be with the same provider. Your domain can remain with your previous registrar while your website and, if applicable, email are operated through CURIAWEB.

Do I have to transfer my domain to CURIAWEB? #

No.

A domain transfer is not required to use an existing domain with CURIAWEB hosting.

For example, you can:

• continue to manage and renew the domain with the current registrar,
• host the website on CURIAWEB,
• and optionally host the email services with CURIAWEB or another provider.

These components are technically separated from each other.

We explain the differences between registrar, registry, DNS, and hosting at Registry and Registrar: What is the difference?.

How do I connect an external domain to CURIAWEB? #

Basically, there are two sensible options.

Option 1: You change the nameservers at your current registrar to the CURIAWEB nameservers. The DNS zone will then be managed via the CURIAWEB infrastructure.

Variant 2: You leave the previous nameservers unchanged and only adjust the DNS records at the currently responsible DNS provider that should point to CURIAWEB.

Which variant makes more sense depends in particular on where you run your website, email, and other services, and where you want to manage the DNS zone in the long term.

Variant 1: Use CURIAWEB nameserver #

If CURIAWEB is to manage your domain's DNS zone, you can enter the following name servers with your current registrar:

ns1.curiaweb.ch
ns2.curiaweb.ch

Following the change of the name servers, the DNS authority is delegated accordingly to the CURIAWEB name servers.

The domain itself still remains registered with the previous registrar.

An example:

Domain registration: previous registrar
Nameservers:          CURIAWEB
Web hosting:          CURIAWEB

This configuration is technically completely normal.

You can find further information about the transition at Finding and correctly using CURIAWEB nameservers.

What do I need to consider before changing nameservers? #

A nameserver change does not only affect the website.

The previous DNS zone may contain additional entries that are still required. These include, for example, entries for:

• Email
• Subdomains
• SPF
• DKIM
• DMARC
• external services
• Domain Verifications

Before the switch, you should therefore check which DNS records currently exist and which of them will still be needed.

With the CURIAWEB DNS-Check can you check publicly visible DNS information of your domain.

You can find a detailed guide on this at Check DNS records: View current DNS configuration of a domain.

Attention: Do not change the nameservers of a domain in production use without first considering the existing DNS configuration. Missing MX, TXT, or other records can, for example, disrupt email traffic or external services.

Option 2: Keep existing nameservers #

You don't necessarily have to use the CURIAWEB nameservers.

If the DNS zone is still to be managed by the previous provider, the existing nameservers remain unchanged.

In this case, you only adjust the DNS records there that are required for CURIAWEB hosting.

An example:

Domain registration: previous registrar
Nameserver:          previous DNS provider
Webhosting:          CURIAWEB

So the DNS zone remains where it is already managed. Only the corresponding records are set to the destinations intended for CURIAWEB hosting.

Which DNS records do I need to change for the website? #

Which entries are required depends on the specific configuration of your domain and your hosting.

Typically, an A record plays an important role for the main domain. This connects a hostname with an IPv4 address.

For:

www.meine-firma.ch

depending on the configuration, an additional custom A-record or a CNAME can also be used.

If IPv6 is used for the hosting in question, an AAAA record may also be relevant.

Important: Use the actual target values from your CURIAWEB hosting details. Do not use IP addresses or DNS values from examples in knowledge base articles.

We explain the function of the various DNS record types at DNS Records Explained: A, AAAA, CNAME, MX, TXT, and CAA.

Where do I find the correct IP address for my CURIAWEB hosting? #

The required server address depends on your specific hosting. Therefore, no general CURIAWEB IP address from a third-party guide or another hosting account should be used.

Use exclusively the server or DNS information intended for your own hosting.

If you are unsure which IP address or DNS value should be used for your domain, you should clarify this before making the change.

Do I also need to change the MX record? #

Not necessarily.

The MX record determines which mail servers accept emails for your domain. It is therefore to be considered independently of where the website points.

If you only move the website for CURIAWEB and want to continue using your existing email solution, the required MX records should generally be kept.

If email is also to be operated via CURIAWEB or the infrastructure provided for this purpose in the future, the email configuration must be set up accordingly.

Note: Website and email are two different services. Changing the A record for the website does not automatically mean that the MX records also need to be changed.

Can my website be hosted with CURIAWEB and my email with another provider? #

Yes.

This is a common configuration.

For example, it can:

Website: CURIAWEB
E-Mail: External email provider
Domain: Previous registrar

be used.

The DNS zone must then contain the appropriate entries for both services.

The A or AAAA record of the website can point to the CURIAWEB hosting infrastructure, while MX and other email-relevant records continue to point to the external email service.

Can I continue to use Microsoft 365 or Google Workspace? #

Basically yes.

If your email is hosted by an external service, your website and email can be configured independently of each other.

It is important that the DNS records provided by the respective email provider are retained or correctly set up in the currently authoritative DNS zone.

In addition to MX records, this can also include TXT, CNAME, or other records.

Therefore, these entries must be taken into account on the new DNS infrastructure when changing name servers.

Can I use SpamExperts with an externally registered domain? #

Yes. What matters is not which registrar the domain is registered with, but whether the required DNS and mail server settings can be configured correctly.

When SpamExperts Incoming Filtering is used, the domain's MX records point to the designated SpamExperts infrastructure.

We explain the setup at Set up SpamExperts incoming filtering and configure MX records.

Must the domain be set up in CURIAWEB hosting first? #

Yes, the domain must be known to the intended hosting environment so that the web server can correctly process requests for this domain name.

Just changing the A-record to a server IP is not necessarily enough.

The web server needs to know which website should be served for the domain in question.

Important: DNS and web server configuration work together. A correct DNS record alone does not create a website and does not automatically assign the correct content to a domain.

What about SSL/TLS? #

If the domain points to CURIAWEB hosting and is correctly configured there, a valid TLS certificate must also exist for the hostnames used.

During a transition, certificate issuance or activation may depend on the domain already pointing correctly to the intended hosting infrastructure.

If DNS is already correct, but the browser continues to display a certificate warning, the SSL/TLS configuration should therefore be checked separately.

What happens to my website with my current provider? #

Changing the DNS records does not delete the previous website.

The files and databases will initially remain on the previous server.

DNS merely determines which technical destination visitors reach for the domain.

When the domain points to CURIAWEB after the switch, visitors will see the website from the new hosting environment—provided it has been fully set up there.

The old hosting environment should therefore not be prematurely deleted or canceled.

When should I cancel my previous hosting? #

Only when the migration has been completely finished and verified.

Before a termination, it should be ensured in particular that:

• the website is completely available on CURIAWEB
• the domain correctly points to the new environment
• HTTPS works
• Forms and other website functions have been tested
• the desired email configuration works
• no required files or databases are left exclusively with the previous provider

Practical Tip: Do not cancel your old hosting before the DNS switch. A brief overlap of both hosting environments facilitates a controlled transition and gives you a fallback option in case something is still missing.

How can I check if everything is ready before the transition? #

Before making the actual DNS change, the new hosting environment should be prepared as completely as possible.

This includes website files, databases, domain configuration, and – if also migrated – the email accounts.

In addition, you should document the existing DNS configuration so that no required entries are lost.

Especially for domains that use services other than websites and email, a DNS zone can contain significantly more than just an A and an MX record.

How can I check if the domain is already pointing to CURIAWEB? #

After the change, you can use the CURIAWEB DNS-Check check which DNS information is currently publicly visible.

If you only changed the A record, you compare the displayed IP address with the value intended for your hosting.

When changing nameservers, you also check whether the domain is already using the CURIAWEB nameservers:

ns1.curiaweb.ch
ns2.curiaweb.ch

We explain the systematic procedure at Check DNS records: View current DNS configuration of a domain.

Why am I still seeing the old website after making the change? #

If the DNS configuration has just been changed, DNS resolvers may temporarily still have older information cached.

As a result, one user can already reach the new hosting infrastructure while another is still directed to the previous server.

This behavior is frequently referred to as DNS propagation.

We explain the technical background at What is DNS propagation and why does a DNS change take time?.

However, not every incorrect website should automatically be explained by DNS propagation. If the authoritative DNS data already points to the wrong target, the configuration must be corrected.

Why isn't the website working after the switch? #

If the domain does not work as expected after a change, you should check the individual levels separately.

First, check which name servers are actually responsible and to which IP address the hostname in question resolves.

If DNS is correct, the cause may lie in the hosting or website configuration.

Possible causes include, for example:

• The domain has not been set up in hosting yet.
• The website files are missing
• The database was not migrated correctly
• the application is still using old URLs
• HTTPS is not yet configured correctly
• a redirection points to an incorrect destination

Why does the website work, but email doesn't? #

If the website is accessible correctly, but emails are not arriving, you should examine the email configuration separately.

A working A record for the website says nothing about whether the MX records are correct.

Check in particular which mail servers are published via DNS and whether they correspond to the desired email infrastructure.

You can find detailed troubleshooting at Emails not arriving: Systematically checking causes.

Changing nameservers or individual DNS records – which option is better? #

There is no single correct answer for every domain.

The use of the CURIAWEB nameservers is particularly practical if DNS management is to be maintained together with hosting.

Retaining the existing nameservers, on the other hand, can be useful if a complex DNS infrastructure is already operated there or if multiple external services depend on it.

What is crucial is that it is clearly defined, where the authoritative DNS zone is managed.

When does a domain transfer make sense? #

A domain transfer can be useful if you also want to consolidate your domain management with CURIAWEB in addition to hosting.

Then, for example, domain management and renewal are handled through the same provider.

However, this transfer is not technically necessary for the use of the hosting.

We explain how a transfer works in the next topic block under Domain transfer to CURIAWEB: How the transfer works.

Note: If you only want to change the hosting, a suitable DNS configuration is sufficient. If you also want to transfer the domain management to CURIAWEB, a domain transfer is an option.

What is the difference between a hosting transfer and a domain transfer? #

At a Hosting change website, databases, and, if applicable, email services are being migrated to a different hosting infrastructure.

At a Domain transfer however, if the registrar of the domain changes.

Both processes can be carried out together, but they are technically independent of each other.

Therefore, you can:

• just change the hosting
• transfer only the domain
• or transfer hosting and domain management together

Especially with an existing website, it makes sense to deliberately distinguish between these processes.

A sensible process for an external domain #

1. First, set up the domain and website in CURIAWEB hosting.
2. Transfer website files and databases if an existing website is being migrated.
3. Document the existing DNS and email configuration.
4. Decide whether you want to use the CURIAWEB nameservers or keep your existing DNS zone.
5. Then specifically change the nameservers or the required DNS records.
6. Check the publicly visible DNS data.
7. Test website, HTTPS, email, and important website functions.
8. Do not cancel the previous hosting environment until the migration is completely finished.

This sequence reduces the risk of unnecessary interruptions.

Summary #

You can leave a domain registered with your current provider and still use CURIAWEB hosting.

Essentially, two options are available for this: You use the CURIAWEB nameservers ns1.curiaweb.ch and ns2.curiaweb.ch or you keep the previous nameservers and only adjust the required DNS records there.

Which variant makes more sense depends on where the website, email, and other services are to be hosted and where the DNS zone is to be managed.

A domain transfer is not required to use CURIAWEB hosting. It only becomes relevant if you also want to transfer the management and renewal of the domain to CURIAWEB.

For an existing domain, the DNS configuration should always be documented first and the new hosting environment fully prepared. This allows the website, email, and other services to be migrated in a controlled manner without unnecessarily changing multiple components at the same time.