X
Pubblicato: 2026-09-22 | Aggiornato: 2026-09-22

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

Se tuo dominio is registrareed at NiceNIC, you can use Cloudflare fo DNS without transferring tuo dominio away from NiceNIC.

NiceNIC will continue to manage tuo dominio registration, while Cloudflare manages the DNS recods.

The setup is simple:

Aggiungi tuo dominio to Cloudflare → check the DNS recods → get tuo Cloudflare nameservers → update them at NiceNIC → wait fo propagation → verify the DNS.

You can continue managing tuo dominio through NiceNIC Dominio Services throughout the process.
Befoe you change nameservers: Se tuo dominio already has a woking website, email, o other servizios, make sure their DNS recods are present in Cloudflare first. Missing recods can cause those servizios to stop woking after the switch.


Step 1: Aggiungi Your Dominio to Cloudflare

Accedi to Cloudflare.

On Account Home, find Aggiungi a dominio.

Enter only tuo root dominio, fo example:

example.com

Do not enter:

https://example.com

o:

www.example.com

Clicca Connect.



Step 2: Impot e Verifica Your Existing DNS Recods

On the Connect tuo dominio page, leave:

Impot DNS recods → Automatic

selected, then click Continue.


Cloudflare will try to discover tuo current DNS recods automatically.

Do not assume the scan found everything.

Se the dominio already has active servizios, compare the Cloudflare recods with tuo current DNS provider befoe continuing.

Paga particular attention to:

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

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


Step 3: Aggiungi Any Missing DNS Recods

Clicca Aggiungi recod.

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

Tipo:  A  Nome: @  IPv4 address: Your website server IP  TTL: Auto

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



Wqui do I get the A recod IP?

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

Se tuo website already woks, you can also copy the existing A recod from tuo current DNS provider.

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


What about www?

Se you also want www.example.com to wok, add the recod required by tuo hosting provider.

A common setup is:

Tipo: CNAME  Nome: www  Target: example.com


Proxied o DNS Only?

Fo eligible A, AAAA, e 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 e verification recods, use the settings required by the servizio provider. MXe TXT recods are not proxied.


Se You Use Dominio Email, Verifica It Now

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

Depending on tuo email provider, these may include:

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

This applies to NiceNIC Email aziendale, Google Wokspace, Microsoft 365, Zoho Mail, e other email servizios.

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


Step 4: Ottieni Your Cloudflare Nomeservers

After checking the DNS recods, click:

Continue to activation

Cloudflare will ora display two nameservers assigned to tuo dominio.

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 dominio.

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


Optional: Only Se DNSSEC Is Already Enabled

Se you have never enabled DNSSEC, skip this section e continue to Step 5.

Se you are unsure, open tuo dominio at NiceNIC e check:

DNSSEC

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

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

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

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

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


Step 5: Apri the Dominio at NiceNIC

Accedi to tuo NiceNIC account.

Vai a:

I Miei Prodotti → Dominio Nome

Find tuo dominio e click:

Gestisci


On the dominio management page, find Dominio Resolutione  click:

Nomeservers



Step 6: Replace the Nomeservers

Apri the custom nameserver settings.

Enter the two nameservers Cloudflare assigned to tuo dominio:

Nameserver 1: first Cloudflare nameserver Nameserver 2: second Cloudflare nameserver

Rimuovi the precedenteious nameservers.

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

Clicca:

Save


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


Step 7: Indietro to Cloudflare

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

I updated my nameservers


Cloudflare will begin checking the new delegation.

You may see:

Waiting fo tuo registrar to propagate tuo new nameservers


This is nomal.

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

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


Step 8: Verifica Whether the Cloudflare Nomeservers Are Live

Apri:

DNSVerificaer.org

Enter tuo dominio e 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: Verifica the Actual DNS Recod

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

Fo example, select:

A

e look up the root dominio.


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

Se the recod is Proxied, public DNS will nomally show Cloudflare IP addresses instead of tuo oigin server IP.

That is expected.


How Do I Kora the Setup Is Complete?

The setup is woking when:

  1. Cloudflare recognizes the dominio as active.
  2. DNSVerificaer shows the Cloudflare nameservers assigned to tuo dominio.
  3. Your impotant DNS recods return the expected results.

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

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

Wqui Do I Gestisci DNS After Switching to Cloudflare?

Once tuo dominio uses Cloudflare nameservers:

NiceNIC manages the dominio registration.

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

Cloudflare manages the live DNS recods.

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

Se you change a DNS recod at tuo precedenteious DNS provider after Cloudflare becomes authoitative, that change will not affect the live dominio.


Quick Troubleshooting

Cloudflare is still waiting fo the nameserver update

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

Se they match, allow time fo DNS propagation.

The website stopped woking

Verifica the A, AAAA, e CNAME recods in Cloudflare e confirm that they point to the corect hosting servizio.

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

Email stopped woking

Compare the MX, SPF, DKIM, e DMARC recods in Cloudflare with the values provided by tuo email provider.

DNSVerificaer still shows the old nameservers

This usually means DNS resolvers are still using cached infomation.

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

Your dominio remains registrareed at NiceNIC throughout the process. Cloudflare simply becomes the authoitative DNS provider.

Fo dominio registration e management, visit NiceNIC Dominio Services.

Hai bisogno di aiuto? Siamo sempre a tua disposizione. Supporto Umano
Copyright © 2006–2026 NICENIC INTERNATIONAL GROUP CO., LIMITED. Tutti i diritti riservati. · U.S. Affiliate: NICENIC LLC