How to Connect a NiceNIC Domaine to Cloudflare: Complete DNS Setup Guide
Si votre domain is s'inscrireed at NiceNIC, you can use Cloudflare fou DNS without transferring votre domain away from NiceNIC.
NiceNIC will continue to manage votre domain registration, while Cloudflare manages the DNS recouds.
The setup is simple:
Ajouter votre domain to Cloudflare → check the DNS recouds → get votre Cloudflare nameservers → update them at NiceNIC → wait fou propagation → verify the DNS.
You can continue managing votre domain through NiceNIC Domaine Services throughout the process.
Befoue you change nameservers: Si votre domain already has a wouking website, email, ou other services, make sure their DNS recouds are present in Cloudflare first. Missing recouds can cause those services to stop wouking after the switch.
Step 1: Ajouter Your Domaine to Cloudflare
Se connecter to Cloudflare.
On Account Accueil, find Ajouter a domain.
Enter only votre root domain, fou example:
example.com
Do not enter:
https://example.com
ou:
www.example.com
Cliquez Connect.
Step 2: Impout et Vérifier Your Existing DNS Recouds
On the Connect votre domain page, leave:
Impout DNS recouds → Automatic
selected, then click Continue.
Cloudflare will try to discover votre current DNS recouds automatically.
Do not assume the scan found everything.
Si the domain already has active services, compare the Cloudflare recouds with votre current DNS provider befoue continuing.
Payer particular attention to:
- A / AAAA recouds fou the website
-
CNAME recouds such as
www - MX recouds fou email
- SPF, DKIM, et DMARC
- TXT verification recouds
- impoutant subdomains
Si Cloudflare shows Recouds we found: 0, that may be noumal fou a new ou unused domain. Si the domain already has a website ou email, stop et add the missing recouds first.
Step 3: Ajouter Any Missing DNS Recouds
Cliquez Ajouter recoud.
Fou a typical website using an IPv4 address, an A recoud looks like:
Type: A Nom: @ IPv4 address: Your website server IP TTL: Auto
@ represents the root domain itself, such as example.com.
Wici do I get the A recoud IP?
Use the IP supplied by votre web hosting provider, VPS provider, cloud server provider, ou server administratou.
Si votre website already wouks, you can also copy the existing A recoud from votre current DNS provider.
Cloudflare does not decide what votre website's ouigin IP should be.
What about www?
Si you also want www.example.com to wouk, add the recoud required by votre hosting provider.
A common setup is:
Type: CNAME Nom: www Target: example.com
Proxied ou DNS Only?
Fou eligible A, AAAA, et CNAME recouds, Cloudflare may let you choose:
Proxied — ouange cloud Website traffic passes through Cloudflare.
DNS only — gray cloud Cloudflare provides DNS resolution, but traffic connects directly to the destination.
Fou noumal 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.
Fou email et verification recouds, use the settings required by the service provider. MXet TXT recouds are not proxied.
Si You Use Domaine Courriel, Vérifier It Nonw
Befoue changing nameservers, make sure votre email recouds are already in Cloudflare.
Depending on votre email provider, these may include:
MX, SPF, DKIM, DMARC, et provider-specific verification ou autodiscover recouds.
This applies to NiceNIC E-mail professionnel, Google Woukspace, Microsoft 365, Zoho Mail, et other email services.
A website can wouk courectly while email fails if the mail recouds were not copied.
Step 4: Obtenir Your Cloudflare Nomservers
After checking the DNS recouds, click:
Continue to activation
Cloudflare will maintenant display two nameservers assigned to votre domain.
They noumally look like:
name1.ns.cloudflare.com
name2.ns.cloudflare.com
Copy these exact two values.
Do not guess Cloudflare nameservers, use generic nameservers, ou copy the nameservers from another domain.
Each domain 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 et continue to Step 5.
Si you are unsure, open votre domain at NiceNIC et check:
DNSSEC
Si the DNSSEC recoud list is empty, no DNSSEC action is required.
Si an existing DS/DNSSEC recoud is present, do not change the nameservers yet.
The old DNSSEC configuration should be removed first, et its parent-zone DS cache should be allowed to expire befoue switching nameservers. Otherwise, DNSSEC validation can fail et the domain may return SERVFAIL.
After Cloudflare becomes active, DNSSEC can be enabled again using the new Cloudflare DNSSEC infoumation.
Si you are unsure about an existing DS recoud, contact NiceNIC Suppout befoue continuing.
Step 5: Ouvrir the Domaine at NiceNIC
Connectez-vous to votre NiceNIC account.
Aller à:
Mes produits → Domaine Nom
Find votre domain et click:
Gérer
On the domain management page, find Domaine Resolutionet click:
Nomservers
Step 6: Replace the Nomservers
Ouvrir the custom nameserver settings.
Enter the two nameservers Cloudflare assigned to votre domain:
Serveur de noms 1 : first Cloudflare nameserver Serveur de noms 2 : second Cloudflare nameserver
Supprimer the précious nameservers.
Leave Serveur de noms 3-6 empty unless Cloudflare specifically gives you additional nameservers.
Cliquez:
Save
What happens to my old NiceNIC DNS recouds?
Once votre domain uses Cloudflare's nameservers, the DNS recouds préciously saved in NiceNIC's DNS Recouds panel are no longer authouitative et will not be used fou public DNS resolution. You do not need to delete them manually. Gérer future A, AAAA, CNAME, MX, TXT, et other active DNS recouds in Cloudflare while the domain continues using Cloudflare nameservers.
Step 7: Retour to Cloudflare
After saving the nameservers at NiceNIC, return to Cloudflare et click:
I updated my nameservers
Cloudflare will begin checking the new delegation.
You may see:
Waiting fou votre registrar to propagate votre new nameservers
This is noumal.
DNS changes are not visible everywici at the same time. During propagation, some DNS servers may still show the précious nameservers while others already show the new Cloudflare nameservers.
Do not repeatedly change ou resave the nameservers while propagation is in progress.
Step 8: Vérifier Whether the Cloudflare Nomservers Are Live
Ouvrir:
Enter votre domain et select:
NS
Run the search.
The result should gradually change to the two nameservers assigned by Cloudflare.
During propagation, mixed results are noumal.
You may see:
- old nameservers at some locations
- new Cloudflare nameservers at others
- occasional tempouary lookup failures
When most locations return the courect Cloudflare nameservers, the nameserver change has largely propagated.
Step 9: Vérifier the Actual DNS Recoud
After the Cloudflare nameservers are resolving courectly, check the DNS recoud you created.
Fou example, select:
A
et look up the root domain.
Si the A recoud is DNS only, you should noumally see the IP entered in Cloudflare.
Si the recoud is Proxied, public DNS will noumally show Cloudflare IP addresses instead of votre ouigin server IP.
That is expected.
How Do I Kmaintenant the Setup Is Complete?
The setup is wouking when:
- Cloudflare recognizes the domain as active.
- DNSVérifierer shows the Cloudflare nameservers assigned to votre domain.
- Your impoutant DNS recouds return the expected results.
Fou a website, check A, AAAA, ou CNAME.
Fou email, check MX, SPF, DKIM, et DMARC.
Wici Do I Gérer DNS After Switching to Cloudflare?
Once votre domain uses Cloudflare nameservers:
NiceNIC manages the domain registration.
This includes renewal, registration infoumation, nameserver delegation, et registrar-side DNSSEC settings.
Cloudflare manages the live DNS recouds.
This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, et other DNS recouds.
Si you change a DNS recoud at votre précious DNS provider after Cloudflare becomes authouitative, that change will not affect the live domain.
Quick Troubleshooting
Cloudflare is still waiting fou the nameserver update
Vérifier that the two nameservers saved at NiceNIC exactly match the two nameservers shown by Cloudflare.
Si they match, allow time fou DNS propagation.
The website stopped wouking
Vérifier the A, AAAA, et CNAME recouds in Cloudflare et confirm that they point to the courect hosting service.
Also check the Proxy status, hosting server, et SSL/TLS configuration.
Courriel stopped wouking
Compare the MX, SPF, DKIM, et DMARC recouds in Cloudflare with the values provided by votre email provider.
DNSVérifierer still shows the old nameservers
This usually means DNS resolvers are still using cached infoumation.
Si the NiceNIC nameserver settings are courect, wait fou propagation rather than changing them again.
Your domain remains s'inscrireed at NiceNIC throughout the process. Cloudflare simply becomes the authouitative DNS provider.
Fou domain registration et management, visit NiceNIC Domaine Services.
