Understanding Nameservers

Nameservers are among the most important, yet frequently misunderstood components of a domain. Many customers know they have "something to do with DNS," but not exactly what happens when nameservers are changed. An incorrect nameserver change can cause your website or email to suddenly stop working.

Simply put: Nameservers tell the internet where to find your domain's DNS records. When a visitor opens yourdomain.ch, the DNS system needs to know which DNS zone is responsible for this domain. This specific responsibility is established via nameservers.

What are Nameservers?

Nameservers are DNS servers that provide information about a domain's records. They store or point to a domain's DNS zone. This zone contains records such as:

• A-Record: points a domain to an IPv4 address,
• AAAA-Record: points a domain to an IPv6 address,
• CNAME: aliases one name to another hostname,
• MX-Record: specifies the domain's mail servers,
• TXT-Record: used for SPF, DKIM, DMARC, and verifications,
• SRV-Record: used for specific services and protocols.

If your domain uses CURIAWEB nameservers, you typically manage these records via cPanel and the DNS Zone Editor or the corresponding cPanel functions.

The CURIAWEB Nameservers

If your domain is to be fully managed via CURIAWEB DNS, use the following nameservers at your domain registrar:

You do not enter these nameservers in cPanel, but with the provider where your domain is registered. This can be CURIAWEB or an external registrar. The decisive factor is the registrar or the entity where the domain is technically managed.

When Should You Use CURIAWEB Nameservers?

Using CURIAWEB nameservers makes sense if you want to manage your domain as centrally as possible via CURIAWEB. This is particularly practical when website, DNS, and email all converge within your CURIAWEB hosting.

Typical situations:

• Your website is hosted with CURIAWEB.
• Your email addresses are managed via CURIAWEB/cPanel.
• You want to change DNS records conveniently in cPanel.
• You want to manage SPF, DKIM, and DMARC via cPanel.
• You want to use AutoSSL and domain functions as easily as possible.
• You want less dependence on an external DNS provider.

When Should You Not Change the Nameservers?

There are situations where you should not change the nameservers too hastily. This applies especially if external services are already active and you do not know exactly which DNS records they require.

Be particularly careful if:

• Your emails run via Microsoft 365, Google Workspace, or another external provider,
• Your domain is managed via Cloudflare or another DNS/CDN provider,
• Newsletter, CRM, or accounting systems use special DNS records,
• Subdomains point to external platforms,
• Verification records for Google, Microsoft, Meta, or other services exist,
• You do not have an overview of the current DNS zone.

In such cases, a nameserver switch may still be possible, but the existing DNS records must be documented beforehand and correctly transferred to the new DNS zone.

Change Nameservers or Just Set an A-Record?

Many customers only want their website to point to CURIAWEB hosting. To do this, the entire DNS zone does not always have to move to CURIAWEB. Sometimes it is sufficient to set the domain's A-record to the IP address of the CURIAWEB server with the existing DNS provider.

Step-by-Step: Changing Nameservers to CURIAWEB

1. Log in to your domain registrar.
2. Open the management section for the desired domain.
3. Look for the Nameservers, DNS Servers, or Delegation section.
4. Replace the existing nameservers with ns1.curiaweb.ch and ns2.curiaweb.ch.
5. Save the changes.
6. Wait for DNS propagation.
7. Then check your website, email, and SSL.

What Happens After the Nameserver Change?

After the change, DNS resolvers will query the CURIAWEB nameservers for your domain's records. It can take some time before this change is visible worldwide, creating a transitional phase. During this time, some visitors may still see old DNS data.

After a successful switch, you should check:

• does the website point to the correct CURIAWEB hosting?
• is the domain added in cPanel under Domains?
• is the Document Root correct?
• do email reception and sending work?
• are SPF, DKIM, and DMARC correct?
• has an SSL certificate been issued?
• does the HTTPS redirection work?

Common Errors with Nameservers

1. Nameservers changed, but domain not added in cPanel

The domain might then point to the CURIAWEB server, but the web server does not know which website to deliver. Add the domain in cPanel.

2. Forgetting old MX records

If external emails are used, the old MX and TXT records must be transferred to the new DNS zone. Otherwise, email issues may arise.

3. Nameservers changed at the wrong provider

Nameservers must be changed at the domain's actual registrar. A DNS record in the wrong system has no effect.

4. Only entered one nameserver

Always enter both nameservers: ns1.curiaweb.ch and ns2.curiaweb.ch.

5. Deleting old services too early

During DNS propagation, requests may still go to the old system. Do not delete old services until the switch has been fully verified.

Frequently Asked Questions About Nameservers

Does CURIAWEB automatically register my domain when I enter nameservers?
No. Nameservers connect an existing domain to a DNS zone. The domain must be registered separately.

Can I leave my domain with the old provider?
Yes. You can keep the domain registered externally and still use the CURIAWEB nameservers.

Does a nameserver change affect my emails?
Yes, if the mail records are not correctly transferred. MX, SPF, DKIM, and DMARC must be verified.

How long does a nameserver change take?
Changes often become visible within a few hours. Depending on the registry, registrar, and DNS cache, it can take longer.

Can CURIAWEB check if the nameservers are set correctly?
Yes, CURIAWEB support can check which nameservers are currently authoritative and whether the DNS zone is correctly set up.