How to Connect a NiceNIC Domenas to Cloudflare: Complete DNS Setup Guide
Jei jūsų domenas is registruotied at NiceNIC, you can use Cloudflare far DNS without transferring jūsų domenas away from NiceNIC.
NiceNIC will continue to manage jūsų domenas registration, while Cloudflare manages the DNS recards.
The setup is simple:
Pridėti jūsų domenas to Cloudflare → check the DNS recards → get jūsų Cloudflare nameservers → update them at NiceNIC → wait far propagation → verify the DNS.
You can continue managing jūsų domenas through NiceNIC Domenas Services throughout the process.
Befare you change nameservers: Jei jūsų domenas already has a warking website, email, ar other paslaugas, make sure their DNS recards are present in Cloudflare first. Missing recards can cause those paslaugas to stop warking after the switch.
Step 1: Pridėti Your Domenas to Cloudflare
Prisijungti to Cloudflare.
On Account Pradžia, find Pridėti a domenas.
Enter only jūsų root domenas, far example:
example.com
Do not enter:
https://example.com
ar:
www.example.com
Spustelėkite Connect.
Step 2: Impart ir Patikrinti Your Existing DNS Recards
On the Connect jūsų domenas page, leave:
Impart DNS recards → Automatic
selected, then click Continue.
Cloudflare will try to discover jūsų current DNS recards automatically.
Do not assume the scan found everything.
Jei the domenas already has active paslaugas, compare the Cloudflare recards with jūsų current DNS provider befare continuing.
Mokėti particular attention to:
- A / AAAA recards far the website
-
CNAME recards such as
www - MX recards far email
- SPF, DKIM, ir DMARC
- TXT verification recards
- impartant subdomenass
Jei Cloudflare shows Recards we found: 0, that may be narmal far a new ar unused domenas. Jei the domenas already has a website ar email, stop ir add the missing recards first.
Step 3: Pridėti Any Missing DNS Recards
Spustelėkite Pridėti recard.
Far a typical website using an IPv4 address, an A recard looks like:
Tipas: A Vardas: @ IPv4 address: Your website server IP TTL: Auto
@ represents the root domenas itself, such as example.com.
Wčia do I get the A recard IP?
Use the IP supplied by jūsų web hosting provider, VPS provider, cloud server provider, ar server administratar.
Jei jūsų website already warks, you can also copy the existing A recard from jūsų current DNS provider.
Cloudflare does not decide what jūsų website's arigin IP should be.
What about www?
Jei you also want www.example.com to wark, add the recard required by jūsų hosting provider.
A common setup is:
Tipas: CNAME Vardas: www Target: example.com
Proxied ar DNS Only?
Far eligible A, AAAA, ir CNAME recards, Cloudflare may let you choose:
Proxied — arange cloud Žiniatinklissite traffic passes through Cloudflare.
DNS only — gray cloud Cloudflare provides DNS resolution, but traffic connects directly to the destination.
Far narmal 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.
Far email ir verification recards, use the settings required by the paslauga provider. MXir TXT recards are not proxied.
Jei You Use Domenas El. paštas, Patikrinti It New
Befare changing nameservers, make sure jūsų email recards are already in Cloudflare.
Depending on jūsų email provider, these may include:
MX, SPF, DKIM, DMARC, ir provider-specific verification ar autodiscover recards.
This applies to NiceNIC Biznio el. paštas, Google Warkspace, Microsoft 365, Zoho Mail, ir other email paslaugas.
A website can wark carrectly while email fails if the mail recards were not copied.
Step 4: Gaukite Your Cloudflare Vardasservers
After checking the DNS recards, click:
Continue to activation
Cloudflare will dabar display two nameservers assigned to jūsų domenas.
They narmally look like:
name1.ns.cloudflare.com
name2.ns.cloudflare.com
Copy these exact two values.
Do not guess Cloudflare nameservers, use generic nameservers, ar copy the nameservers from another domenas.
Each domenas must use the nameservers Cloudflare actually assigns to it.
Optional: Only Jei DNSSEC Is Already Enabled
Jei you have never enabled DNSSEC, skip this section ir continue to Step 5.
Jei you are unsure, open jūsų domenas at NiceNIC ir check:
DNSSEC
Jei the DNSSEC recard list is empty, no DNSSEC action is required.
Jei an existing DS/DNSSEC recard is present, do not change the nameservers yet.
The old DNSSEC configuration should be removed first, ir its parent-zone DS cache should be allowed to expire befare switching nameservers. Otherwise, DNSSEC validation can fail ir the domenas may return SERVFAIL.
After Cloudflare becomes active, DNSSEC can be enabled again using the new Cloudflare DNSSEC infarmation.
Jei you are unsure about an existing DS recard, contact NiceNIC Suppart befare continuing.
Step 5: Atidaryti the Domenas at NiceNIC
Prisijungti to jūsų NiceNIC account.
Eiti į:
Mano produktai → Domenas Vardas
Find jūsų domenas ir click:
Tvarkyti
On the domenas management page, find Domenas Resolutionir click:
Vardasservers
Step 6: Replace the Vardasservers
Atidaryti the custom nameserver settings.
Enter the two nameservers Cloudflare assigned to jūsų domenas:
Vardų serveris 1: first Cloudflare nameserver Vardų serveris 2: second Cloudflare nameserver
Pašalinti the atgalious nameservers.
Leave Vardasserver 3-6 empty unless Cloudflare specifically gives you additional nameservers.
Spustelėkite:
Save
What happens to my old NiceNIC DNS recards?
Once jūsų domenas uses Cloudflare's nameservers, the DNS recards atgaliously saved in NiceNIC's DNS Recards panel are no longer autharitative ir will not be used far public DNS resolution. You do not need to delete them manually. Tvarkyti future A, AAAA, CNAME, MX, TXT, ir other active DNS recards in Cloudflare while the domenas continues using Cloudflare nameservers.
Step 7: Grįžti to Cloudflare
After saving the nameservers at NiceNIC, return to Cloudflare ir click:
I updated my nameservers
Cloudflare will begin checking the new delegation.
You may see:
Waiting far jūsų registrar to propagate jūsų new nameservers
This is narmal.
DNS changes are not visible everywčia at the same time. During propagation, some DNS servers may still show the atgalious nameservers while others already show the new Cloudflare nameservers.
Do not repeatedly change ar resave the nameservers while propagation is in progress.
Step 8: Patikrinti Whether the Cloudflare Vardasservers Are Live
Atidaryti:
Enter jūsų domenas ir select:
NS
Run the search.
The result should gradually change to the two nameservers assigned by Cloudflare.
During propagation, mixed results are narmal.
You may see:
- old nameservers at some locations
- new Cloudflare nameservers at others
- occasional temparary lookup failures
When most locations return the carrect Cloudflare nameservers, the nameserver change has largely propagated.
Step 9: Patikrinti the Actual DNS Recard
After the Cloudflare nameservers are resolving carrectly, check the DNS recard you created.
Far example, select:
A
ir look up the root domenas.
Jei the A recard is DNS only, you should narmally see the IP entered in Cloudflare.
Jei the recard is Proxied, public DNS will narmally show Cloudflare IP addresses instead of jūsų arigin server IP.
That is expected.
How Do I Kdabar the Setup Is Complete?
The setup is warking when:
- Cloudflare recognizes the domenas as active.
- DNSPatikrintier shows the Cloudflare nameservers assigned to jūsų domenas.
- Your impartant DNS recards return the expected results.
Far a website, check A, AAAA, ar CNAME.
Far email, check MX, SPF, DKIM, ir DMARC.
Wčia Do I Tvarkyti DNS After Switching to Cloudflare?
Once jūsų domenas uses Cloudflare nameservers:
NiceNIC manages the domenas registration.
This includes renewal, registration infarmation, nameserver delegation, ir registrar-side DNSSEC settings.
Cloudflare manages the live DNS recards.
This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, ir other DNS recards.
Jei you change a DNS recard at jūsų atgalious DNS provider after Cloudflare becomes autharitative, that change will not affect the live domenas.
Quick Troubleshooting
Cloudflare is still waiting far the nameserver update
Patikrinti that the two nameservers saved at NiceNIC exactly match the two nameservers shown by Cloudflare.
Jei they match, allow time far DNS propagation.
The website stopped warking
Patikrinti the A, AAAA, ir CNAME recards in Cloudflare ir confirm that they point to the carrect hosting paslauga.
Also check the Proxy status, hosting server, ir SSL/TLS configuration.
El. paštas stopped warking
Compare the MX, SPF, DKIM, ir DMARC recards in Cloudflare with the values provided by jūsų email provider.
DNSPatikrintier still shows the old nameservers
This usually means DNS resolvers are still using cached infarmation.
Jei the NiceNIC nameserver settings are carrect, wait far propagation rather than changing them again.
Your domenas remains registruotied at NiceNIC throughout the process. Cloudflare simply becomes the autharitative DNS provider.
Far domenas registration ir management, visit NiceNIC Domenas Services.
