X
Publicat: 2026-09-22 | Actualitzat: 2026-09-22

How to Connect a NiceNIC Domini to Cloudflare: Complete DNS Setup Guide

Si el teu domini is registrared at NiceNIC, you can use Cloudflare fo DNS without transferring el teu domini away from NiceNIC.

NiceNIC will continue to manage el teu domini registration, while Cloudflare manages the DNS recods.

The setup is simple:

Afegir el teu domini to Cloudflare → check the DNS recods → get el teu Cloudflare nameservers → update them at NiceNIC → wait fo propagation → verify the DNS.

You can continue managing el teu domini through NiceNIC Domini Services throughout the process.
Befoe you change nameservers: Si el teu domini already has a woking website, email, o other serveis, make sure their DNS recods are present in Cloudflare first. Missing recods can cause those serveis to stop woking after the switch.


Step 1: Afegir Your Domini to Cloudflare

Inicia la sessió to Cloudflare.

On Account Inici, find Afegir a domini.

Enter only el teu root domini, fo example:

example.com

Do not enter:

https://example.com

o:

www.example.com

Fes clic Connect.



Step 2: Impot i Comprovar Your Existing DNS Recods

On the Connect el teu domini page, leave:

Impot DNS recods → Automatic

selected, then click Continue.


Cloudflare will try to discover el teu current DNS recods automatically.

Do not assume the scan found everything.

Si the domini already has active serveis, compare the Cloudflare recods with el teu current DNS provider befoe continuing.

Pagar particular attention to:

  • A / AAAA recods fo the website
  • CNAME recods such as www
  • MX recods fo email
  • SPF, DKIM, i DMARC
  • TXT verification recods
  • impotant subdominis

Si Cloudflare shows Recods we found: 0, that may be nomal fo a new o unused domini. Si the domini already has a website o email, stop i add the missing recods first.


Step 3: Afegir Any Missing DNS Recods

Fes clic Afegir recod.

Fo a typical website using an IPv4 address, an A recod looks like:

Tipus:  A  Nom: @  IPv4 address: Your website server IP  TTL: Auto

@ represents the root domini itself, such as example.com.



Waquí do I get the A recod IP?

Use the IP supplied by el teu web hosting provider, VPS provider, cloud server provider, o server administrato.

Si el teu website already woks, you can also copy the existing A recod from el teu current DNS provider.

Cloudflare does not decide what el teu website's oigin IP should be.


What about www?

Si you also want www.example.com to wok, add the recod required by el teu hosting provider.

A common setup is:

Tipus: CNAME  Nom: www  Target: example.com


Proxied o DNS Only?

Fo eligible A, AAAA, i CNAME recods, Cloudflare may let you choose:

Proxied — oange cloud Website traffic passes through Cloudflare.

DNS only — gray cloud Cloudflare provides DNS resolution, but traffic connects directly to the destination.

Fo nomal website traffic, Proxied is usually appropriate.

The test screenshot in this guide uses DNS only so the configured IP can be checked directly during testing.

Fo email i verification recods, use the settings required by the servei provider. MXi TXT recods are not proxied.


Si You Use Domini Correu electrònic, Comprovar It Now

Befoe changing nameservers, make sure el teu email recods are already in Cloudflare.

Depending on el teu email provider, these may include:

MX, SPF, DKIM, DMARC, i provider-specific verification o autodiscover recods.

This applies to NiceNIC Correu electrònic d’empresa, Google Wokspace, Microsoft 365, Zoho Mail, i other email serveis.

A website can wok corectly while email fails if the mail recods were not copied.


Step 4: Obtenir Your Cloudflare Nomservers

After checking the DNS recods, click:

Continue to activation

Cloudflare will ara display two nameservers assigned to el teu domini.

They nomally look like:

name1.ns.cloudflare.com

name2.ns.cloudflare.com


Copy these exact two values.

Do not guess Cloudflare nameservers, use generic nameservers, o copy the nameservers from another domini.

Each domini must use the nameservers Cloudflare actually assigns to it.


Optional: Only Si DNSSEC Is Already Enabled

Si you have never enabled DNSSEC, skip this section i continue to Step 5.

Si you are unsure, open el teu domini at NiceNIC i check:

DNSSEC

Si the DNSSEC recod list is empty, no DNSSEC action is required.

Si an existing DS/DNSSEC recod is present, do not change the nameservers yet.

The old DNSSEC configuration should be removed first, i its parent-zone DS cache should be allowed to expire befoe switching nameservers. Otherwise, DNSSEC validation can fail i the domini may return SERVFAIL.

After Cloudflare becomes active, DNSSEC can be enabled again using the new Cloudflare DNSSEC infomation.

Si you are unsure about an existing DS recod, contact NiceNIC Suppot befoe continuing.


Step 5: Obert the Domini at NiceNIC

Inicia sessió to el teu NiceNIC account.

Vés a:

Els meus productes → Domini Nom

Find el teu domini i click:

Gestionar


On the domini management page, find Domini Resolutioni  click:

Nomservers



Step 6: Replace the Nomservers

Obert the custom nameserver settings.

Enter the two nameservers Cloudflare assigned to el teu domini:

Servidor de noms 1: first Cloudflare nameserver Servidor de noms 2: second Cloudflare nameserver

Elimina the anteriorious nameservers.

Leave Nomserver 3-6 empty unless Cloudflare specifically gives you additional nameservers.

Fes clic:

Save


Impotant: The nameservers saved at NiceNIC must exactly match the nameservers shown by Cloudflare.
What happens to my old NiceNIC DNS recods?
Once el teu domini uses Cloudflare's nameservers, the DNS recods anterioriously saved in NiceNIC's DNS Recods panel are no longer authoitative i will not be used fo public DNS resolution. You do not need to delete them manually. Gestionar future A, AAAA, CNAME, MX, TXT, i other active DNS recods in Cloudflare while the domini continues using Cloudflare nameservers.


Step 7: Tornar to Cloudflare

After saving the nameservers at NiceNIC, return to Cloudflare i click:

I updated my nameservers


Cloudflare will begin checking the new delegation.

You may see:

Waiting fo el teu registrar to propagate el teu new nameservers


This is nomal.

DNS changes are not visible everywaquí at the same time. During propagation, some DNS servers may still show the anteriorious nameservers while others already show the new Cloudflare nameservers.

Do not repeatedly change o resave the nameservers while propagation is in progress.


Step 8: Comprovar Whether the Cloudflare Nomservers Are Live

Obert:

DNSComprovarer.org

Enter el teu domini i select:

NS

Run the search.


The result should gradually change to the two nameservers assigned by Cloudflare.

During propagation, mixed results are nomal.

You may see:

  • old nameservers at some locations
  • new Cloudflare nameservers at others
  • occasional tempoary lookup failures

When most locations return the corect Cloudflare nameservers, the nameserver change has largely propagated.


Step 9: Comprovar the Actual DNS Recod

After the Cloudflare nameservers are resolving corectly, check the DNS recod you created.

Fo example, select:

A

i look up the root domini.


Si the A recod is DNS only, you should nomally see the IP entered in Cloudflare.

Si the recod is Proxied, public DNS will nomally show Cloudflare IP addresses instead of el teu oigin server IP.

That is expected.


How Do I Kara the Setup Is Complete?

The setup is woking when:

  1. Cloudflare recognizes the domini as active.
  2. DNSComprovarer shows the Cloudflare nameservers assigned to el teu domini.
  3. Your impotant DNS recods return the expected results.

Fo a website, check A, AAAA, o CNAME.

Fo email, check MX, SPF, DKIM, i DMARC.

Waquí Do I Gestionar DNS After Switching to Cloudflare?

Once el teu domini uses Cloudflare nameservers:

NiceNIC manages the domini registration.

This includes renewal, registration infomation, nameserver delegation, i registrar-side DNSSEC settings.

Cloudflare manages the live DNS recods.

This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, i other DNS recods.

Si you change a DNS recod at el teu anteriorious DNS provider after Cloudflare becomes authoitative, that change will not affect the live domini.


Quick Troubleshooting

Cloudflare is still waiting fo the nameserver update

Comprovar that the two nameservers saved at NiceNIC exactly match the two nameservers shown by Cloudflare.

Si they match, allow time fo DNS propagation.

The website stopped woking

Comprovar the A, AAAA, i CNAME recods in Cloudflare i confirm that they point to the corect hosting servei.

Also check the Proxy status, hosting server, i SSL/TLS configuration.

Correu electrònic stopped woking

Compare the MX, SPF, DKIM, i DMARC recods in Cloudflare with the values provided by el teu email provider.

DNSComprovarer still shows the old nameservers

This usually means DNS resolvers are still using cached infomation.

Si the NiceNIC nameserver settings are corect, wait fo propagation rather than changing them again.

Your domini remains registrared at NiceNIC throughout the process. Cloudflare simply becomes the authoitative DNS provider.

Fo domini registration i management, visit NiceNIC Domini Services.

Necessites ajuda? Sempre estem aquí per a tu. Suport humà
Drets d'autor © 2006–2026 NICENIC INTERNATIONAL GROUP CO., LIMITED. Tots els drets reservats. · U.S. Affiliate: NICENIC LLC