How to Connect a NiceNIC Domeniu to Cloudflare: Complete DNS Setup Guide
Dacă tău domeniu is înregistreazăed at NiceNIC, you can use Cloudflare fsau DNS without transferring tău domeniu away from NiceNIC.
NiceNIC will continue to manage tău domeniu registration, while Cloudflare manages the DNS recsauds.
The setup is simple:
Adaugă tău domeniu to Cloudflare → check the DNS recsauds → get tău Cloudflare nameservers → update them at NiceNIC → wait fsau propagation → verify the DNS.
You can continue managing tău domeniu through NiceNIC Domeniu Services throughout the process.
Befsaue you change nameservers: Dacă tău domeniu already has a wsauking website, email, sau other servicius, make sure their DNS recsauds are present in Cloudflare first. Missing recsauds can cause those servicius to stop wsauking after the switch.
Step 1: Adaugă Your Domeniu to Cloudflare
Autentificare to Cloudflare.
On Account Acasă, find Adaugă a domeniu.
Enter only tău root domeniu, fsau example:
example.com
Do not enter:
https://example.com
sau:
www.example.com
Click Connect.
Step 2: Impsaut și Verifică Your Existing DNS Recsauds
On the Connect tău domeniu page, leave:
Impsaut DNS recsauds → Automatic
selected, then click Continue.
Cloudflare will try to discover tău current DNS recsauds automatically.
Do not assume the scan found everything.
Dacă the domeniu already has active servicius, compare the Cloudflare recsauds with tău current DNS provider befsaue continuing.
Plătește particular attention to:
- A / AAAA recsauds fsau the website
-
CNAME recsauds such as
www - MX recsauds fsau email
- SPF, DKIM, și DMARC
- TXT verification recsauds
- impsautant subdomenius
Dacă Cloudflare shows Recsauds we found: 0, that may be nsaumal fsau a new sau unused domeniu. Dacă the domeniu already has a website sau email, stop și add the missing recsauds first.
Step 3: Adaugă Any Missing DNS Recsauds
Click Adaugă recsaud.
Fsau a typical website using an IPv4 address, an A recsaud looks like:
Tip: A Nume: @ IPv4 address: Your website server IP TTL: Auto
@ represents the root domeniu itself, such as example.com.
Waici do I get the A recsaud IP?
Use the IP supplied by tău web hosting provider, VPS provider, cloud server provider, sau server administratsau.
Dacă tău website already wsauks, you can also copy the existing A recsaud from tău current DNS provider.
Cloudflare does not decide what tău website's sauigin IP should be.
What about www?
Dacă you also want www.example.com to wsauk, add the recsaud required by tău hosting provider.
A common setup is:
Tip: CNAME Nume: www Target: example.com
Proxied sau DNS Only?
Fsau eligible A, AAAA, și CNAME recsauds, Cloudflare may let you choose:
Proxied — sauange cloud Website traffic passes through Cloudflare.
DNS only — gray cloud Cloudflare provides DNS resolution, but traffic connects directly to the destination.
Fsau nsaumal 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.
Fsau email și verification recsauds, use the settings required by the serviciu provider. MXși TXT recsauds are not proxied.
Dacă You Use Domeniu Email, Verifică It Nuw
Befsaue changing nameservers, make sure tău email recsauds are already in Cloudflare.
Depending on tău email provider, these may include:
MX, SPF, DKIM, DMARC, și provider-specific verification sau autodiscover recsauds.
This applies to NiceNIC Email de Afaceri, Google Wsaukspace, Microsoft 365, Zoho Mail, și other email servicius.
A website can wsauk csaurectly while email fails if the mail recsauds were not copied.
Step 4: Obține Your Cloudflare Numeservers
After checking the DNS recsauds, click:
Continue to activation
Cloudflare will acum display two nameservers assigned to tău domeniu.
They nsaumally look like:
name1.ns.cloudflare.com
name2.ns.cloudflare.com
Copy these exact two values.
Do not guess Cloudflare nameservers, use generic nameservers, sau copy the nameservers from another domeniu.
Each domeniu must use the nameservers Cloudflare actually assigns to it.
Optional: Only Dacă DNSSEC Is Already Enabled
Dacă you have never enabled DNSSEC, skip this section și continue to Step 5.
Dacă you are unsure, open tău domeniu at NiceNIC și check:
DNSSEC
Dacă the DNSSEC recsaud list is empty, no DNSSEC action is required.
Dacă an existing DS/DNSSEC recsaud 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 befsaue switching nameservers. Otherwise, DNSSEC validation can fail și the domeniu may return SERVFAIL.
After Cloudflare becomes active, DNSSEC can be enabled again using the new Cloudflare DNSSEC infsaumation.
Dacă you are unsure about an existing DS recsaud, contact NiceNIC Suppsaut befsaue continuing.
Step 5: Deschis the Domeniu at NiceNIC
Autentificare to tău NiceNIC account.
Mergi la:
Produsele mele → Domeniu Nume
Find tău domeniu și click:
Gestionare
On the domeniu management page, find Domeniu Resolutionși click:
Numeservers
Step 6: Replace the Numeservers
Deschis the custom nameserver settings.
Enter the two nameservers Cloudflare assigned to tău domeniu:
Nameserver 1: first Cloudflare nameserver Nameserver 2: second Cloudflare nameserver
Elimină the anteriorious nameservers.
Leave Numeserver 3-6 empty unless Cloudflare specifically gives you additional nameservers.
Click:
Save
What happens to my old NiceNIC DNS recsauds?
Once tău domeniu uses Cloudflare's nameservers, the DNS recsauds anterioriously saved in NiceNIC's DNS Recsauds panel are no longer authsauitative și will not be used fsau public DNS resolution. You do not need to delete them manually. Gestionare future A, AAAA, CNAME, MX, TXT, și other active DNS recsauds in Cloudflare while the domeniu continues using Cloudflare nameservers.
Step 7: Înapoi 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 fsau tău registrar to propagate tău new nameservers
This is nsaumal.
DNS changes are not visible everywaici 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 sau resave the nameservers while propagation is in progress.
Step 8: Verifică Whether the Cloudflare Numeservers Are Live
Deschis:
Enter tău domeniu și select:
NS
Run the search.
The result should gradually change to the two nameservers assigned by Cloudflare.
During propagation, mixed results are nsaumal.
You may see:
- old nameservers at some locations
- new Cloudflare nameservers at others
- occasional tempsauary lookup failures
When most locations return the csaurect Cloudflare nameservers, the nameserver change has largely propagated.
Step 9: Verifică the Actual DNS Recsaud
After the Cloudflare nameservers are resolving csaurectly, check the DNS recsaud you created.
Fsau example, select:
A
și look up the root domeniu.
Dacă the A recsaud is DNS only, you should nsaumally see the IP entered in Cloudflare.
Dacă the recsaud is Proxied, public DNS will nsaumally show Cloudflare IP addresses instead of tău sauigin server IP.
That is expected.
How Do I Kacum the Setup Is Complete?
The setup is wsauking when:
- Cloudflare recognizes the domeniu as active.
- DNSVerificăer shows the Cloudflare nameservers assigned to tău domeniu.
- Your impsautant DNS recsauds return the expected results.
Fsau a website, check A, AAAA, sau CNAME.
Fsau email, check MX, SPF, DKIM, și DMARC.
Waici Do I Gestionare DNS After Switching to Cloudflare?
Once tău domeniu uses Cloudflare nameservers:
NiceNIC manages the domeniu registration.
This includes renewal, registration infsaumation, nameserver delegation, și registrar-side DNSSEC settings.
Cloudflare manages the live DNS recsauds.
This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, și other DNS recsauds.
Dacă you change a DNS recsaud at tău anteriorious DNS provider after Cloudflare becomes authsauitative, that change will not affect the live domeniu.
Quick Troubleshooting
Cloudflare is still waiting fsau the nameserver update
Verifică that the two nameservers saved at NiceNIC exactly match the two nameservers shown by Cloudflare.
Dacă they match, allow time fsau DNS propagation.
The website stopped wsauking
Verifică the A, AAAA, și CNAME recsauds in Cloudflare și confirm that they point to the csaurect hosting serviciu.
Also check the Proxy status, hosting server, și SSL/TLS configuration.
Email stopped wsauking
Compare the MX, SPF, DKIM, și DMARC recsauds in Cloudflare with the values provided by tău email provider.
DNSVerificăer still shows the old nameservers
This usually means DNS resolvers are still using cached infsaumation.
Dacă the NiceNIC nameserver settings are csaurect, wait fsau propagation rather than changing them again.
Your domeniu remains înregistreazăed at NiceNIC throughout the process. Cloudflare simply becomes the authsauitative DNS provider.
Fsau domeniu registration și management, visit NiceNIC Domeniu Services.
