How to Connect a NiceNIC Dominio to Cloudflare: Complete DNS Setup Guide
Si tu/tus/su/sus dominio is registrared at NiceNIC, you can use Cloudflare fo DNS without transferring tu/tus/su/sus dominio away from NiceNIC.
NiceNIC will continue to manage tu/tus/su/sus dominio registration, while Cloudflare manages the DNS recods.
The setup is simple:
Agregar tu/tus/su/sus dominio to Cloudflare → check the DNS recods → get tu/tus/su/sus Cloudflare nameservers → update them at NiceNIC → wait fo propagation → verify the DNS.
You can continue managing tu/tus/su/sus dominio through NiceNIC Dominio Services throughout the process.
Befoe you change nameservers: Si tu/tus/su/sus dominio already has a woking website, email, o other servicios, make sure their DNS recods are present in Cloudflare first. Missing recods can cause those servicios to stop woking after the switch.
Step 1: Agregar Your Dominio to Cloudflare
Iniciar Sesión to Cloudflare.
On Account Inicio, find Agregar a dominio.
Enter only tu/tus/su/sus root dominio, fo example:
example.com
Do not enter:
https://example.com
o:
www.example.com
Hacer clic Connect.
Step 2: Impot y Verificar Your Existing DNS Recods
On the Connect tu/tus/su/sus dominio page, leave:
Impot DNS recods → Automatic
selected, then click Continue.
Cloudflare will try to discover tu/tus/su/sus current DNS recods automatically.
Do not assume the scan found everything.
Si the dominio already has active servicios, compare the Cloudflare recods with tu/tus/su/sus 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, y DMARC
- TXT verification recods
- impotant subdominios
Si Cloudflare shows Recods we found: 0, that may be nomal fo a new o unused dominio. Si the dominio already has a website o email, stop y add the missing recods first.
Step 3: Agregar Any Missing DNS Recods
Hacer clic Agregar recod.
Fo a typical website using an IPv4 address, an A recod looks like:
Tipo: A Nombre: @ IPv4 address: Your website server IP TTL: Auto
@ represents the root dominio itself, such as example.com.
Waquí do I get the A recod IP?
Use the IP supplied by tu/tus/su/sus web hosting provider, VPS provider, cloud server provider, o server administrato.
Si tu/tus/su/sus website already woks, you can also copy the existing A recod from tu/tus/su/sus current DNS provider.
Cloudflare does not decide what tu/tus/su/sus website's oigin IP should be.
What about www?
Si you also want www.example.com to wok, add the recod required by tu/tus/su/sus hosting provider.
A common setup is:
Tipo: CNAME Nombre: www Target: example.com
Proxied o DNS Only?
Fo eligible A, AAAA, y 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 y verification recods, use the settings required by the servicio provider. MXy TXT recods are not proxied.
Si You Use Dominio Correo Electrónico, Verificar It Now
Befoe changing nameservers, make sure tu/tus/su/sus email recods are already in Cloudflare.
Depending on tu/tus/su/sus email provider, these may include:
MX, SPF, DKIM, DMARC, y provider-specific verification o autodiscover recods.
This applies to NiceNIC Correo Empresarial, Google Wokspace, Microsoft 365, Zoho Mail, y other email servicios.
A website can wok corectly while email fails if the mail recods were not copied.
Step 4: Obtener Your Cloudflare Nombreservers
After checking the DNS recods, click:
Continue to activation
Cloudflare will ahora display two nameservers assigned to tu/tus/su/sus 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 Si DNSSEC Is Already Enabled
Si you have never enabled DNSSEC, skip this section y continue to Step 5.
Si you are unsure, open tu/tus/su/sus dominio at NiceNIC y 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, y its parent-zone DS cache should be allowed to expire befoe switching nameservers. Otherwise, DNSSEC validation can fail y the dominio 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: Abrir the Dominio at NiceNIC
Iniciar sesión to tu/tus/su/sus NiceNIC account.
Ir a:
Mis Productos → Dominio Nombre
Find tu/tus/su/sus dominio y click:
Gestionar
On the dominio management page, find Dominio Resolutiony click:
Nombreservers
Step 6: Replace the Nombreservers
Abrir the custom nameserver settings.
Enter the two nameservers Cloudflare assigned to tu/tus/su/sus dominio:
Servidor de Nombres 1: first Cloudflare nameserver Servidor de Nombres 2: second Cloudflare nameserver
Eliminar the anteriorious nameservers.
Leave Nombreserver 3-6 empty unless Cloudflare specifically gives you additional nameservers.
Hacer clic:
Save
What happens to my old NiceNIC DNS recods?
Once tu/tus/su/sus dominio uses Cloudflare's nameservers, the DNS recods anterioriously saved in NiceNIC's DNS Recods panel are no longer authoitative y will not be used fo public DNS resolution. You do not need to delete them manually. Gestionar future A, AAAA, CNAME, MX, TXT, y other active DNS recods in Cloudflare while the dominio continues using Cloudflare nameservers.
Step 7: Volver to Cloudflare
After saving the nameservers at NiceNIC, return to Cloudflare y click:
I updated my nameservers
Cloudflare will begin checking the new delegation.
You may see:
Waiting fo tu/tus/su/sus registrar to propagate tu/tus/su/sus 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: Verificar Whether the Cloudflare Nombreservers Are Live
Abrir:
Enter tu/tus/su/sus dominio y 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: Verificar the Actual DNS Recod
After the Cloudflare nameservers are resolving corectly, check the DNS recod you created.
Fo example, select:
A
y look up the root dominio.
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 tu/tus/su/sus oigin server IP.
That is expected.
How Do I Kahora the Setup Is Complete?
The setup is woking when:
- Cloudflare recognizes the dominio as active.
- DNSVerificarer shows the Cloudflare nameservers assigned to tu/tus/su/sus dominio.
- Your impotant DNS recods return the expected results.
Fo a website, check A, AAAA, o CNAME.
Fo email, check MX, SPF, DKIM, y DMARC.
Waquí Do I Gestionar DNS After Switching to Cloudflare?
Once tu/tus/su/sus dominio uses Cloudflare nameservers:
NiceNIC manages the dominio registration.
This includes renewal, registration infomation, nameserver delegation, y registrar-side DNSSEC settings.
Cloudflare manages the live DNS recods.
This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, y other DNS recods.
Si you change a DNS recod at tu/tus/su/sus anteriorious DNS provider after Cloudflare becomes authoitative, that change will not affect the live dominio.
Quick Troubleshooting
Cloudflare is still waiting fo the nameserver update
Verificar 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
Verificar the A, AAAA, y CNAME recods in Cloudflare y confirm that they point to the corect hosting servicio.
Also check the Proxy status, hosting server, y SSL/TLS configuration.
Correo Electrónico stopped woking
Compare the MX, SPF, DKIM, y DMARC recods in Cloudflare with the values provided by tu/tus/su/sus email provider.
DNSVerificarer 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 dominio remains registrared at NiceNIC throughout the process. Cloudflare simply becomes the authoitative DNS provider.
Fo dominio registration y management, visit NiceNIC Dominio Services.
