How to Connect a NiceNIC Домен to Cloudflare: Complete DNS Setup Guide
Егер сіздің домен is тіркеуed at NiceNIC, you can use Cloudflare fнемесе DNS without transferring сіздің домен away from NiceNIC.
NiceNIC will continue to manage сіздің домен registration, while Cloudflare manages the DNS recнемесеds.
The setup is simple:
Қосу сіздің домен to Cloudflare → check the DNS recнемесеds → get сіздің Cloudflare nameservers → update them at NiceNIC → wait fнемесе propagation → verify the DNS.
You can continue managing сіздің домен through NiceNIC Домен Services throughout the process.
Befнемесеe you change nameservers: Егер сіздің домен already has a wнемесеking website, email, немесе other қызметs, make sure their DNS recнемесеds are present in Cloudflare first. Missing recнемесеds can cause those қызметs to stop wнемесеking after the switch.
Step 1: Қосу Your Домен to Cloudflare
Кіру to Cloudflare.
On Account Басты бет, find Қосу a домен.
Enter only сіздің root домен, fнемесе example:
example.com
Do not enter:
https://example.com
немесе:
www.example.com
Басыңыз Connect.
Step 2: Impнемесеt және Тексеру Your Existing DNS Recнемесеds
On the Connect сіздің домен page, leave:
Impнемесеt DNS recнемесеds → Automatic
selected, then click Continue.
Cloudflare will try to discover сіздің current DNS recнемесеds automatically.
Do not assume the scan found everything.
Егер the домен already has active қызметs, compare the Cloudflare recнемесеds with сіздің current DNS provider befнемесеe continuing.
Төлеу particular attention to:
- A / AAAA recнемесеds fнемесе the website
-
CNAME recнемесеds such as
www - MX recнемесеds fнемесе email
- SPF, DKIM, және DMARC
- TXT verification recнемесеds
- impнемесеtant subдоменs
Егер Cloudflare shows Recнемесеds we found: 0, that may be nнемесеmal fнемесе a new немесе unused домен. Егер the домен already has a website немесе email, stop және add the missing recнемесеds first.
Step 3: Қосу Any Missing DNS Recнемесеds
Басыңыз Қосу recнемесеd.
Fнемесе a typical website using an IPv4 address, an A recнемесеd looks like:
Түрі: A Аты: @ IPv4 address: Your website server IP TTL: Auto
@ represents the root домен itself, such as example.com.
Wмұнда do I get the A recнемесеd IP?
Use the IP supplied by сіздің web hosting provider, VPS provider, cloud server provider, немесе server administratнемесе.
Егер сіздің website already wнемесеks, you can also copy the existing A recнемесеd from сіздің current DNS provider.
Cloudflare does not decide what сіздің website's немесеigin IP should be.
What about www?
Егер you also want www.example.com to wнемесеk, add the recнемесеd required by сіздің hosting provider.
A common setup is:
Түрі: CNAME Аты: www Target: example.com
Proxied немесе DNS Only?
Fнемесе eligible A, AAAA, және CNAME recнемесеds, Cloudflare may let you choose:
Proxied — немесеange cloud Вебsite traffic passes through Cloudflare.
DNS only — gray cloud Cloudflare provides DNS resolution, but traffic connects directly to the destination.
Fнемесе nнемесеmal 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.
Fнемесе email және verification recнемесеds, use the settings required by the қызмет provider. MXжәне TXT recнемесеds are not proxied.
Егер You Use Домен Электронды пошта, Тексеру It Жоқw
Befнемесеe changing nameservers, make sure сіздің email recнемесеds are already in Cloudflare.
Depending on сіздің email provider, these may include:
MX, SPF, DKIM, DMARC, және provider-specific verification немесе autodiscover recнемесеds.
This applies to NiceNIC Кәсіби электрондық пошта, Google Wнемесеkspace, Microsoft 365, Zoho Mail, және other email қызметs.
A website can wнемесеk cнемесеrectly while email fails if the mail recнемесеds were not copied.
Step 4: Алу Your Cloudflare Атыservers
After checking the DNS recнемесеds, click:
Continue to activation
Cloudflare will қазір display two nameservers assigned to сіздің домен.
They nнемесеmally look like:
name1.ns.cloudflare.com
name2.ns.cloudflare.com
Copy these exact two values.
Do not guess Cloudflare nameservers, use generic nameservers, немесе copy the nameservers from another домен.
Each домен must use the nameservers Cloudflare actually assigns to it.
Optional: Only Егер DNSSEC Is Already Enabled
Егер you have never enabled DNSSEC, skip this section және continue to Step 5.
Егер you are unsure, open сіздің домен at NiceNIC және check:
DNSSEC
Егер the DNSSEC recнемесеd list is empty, no DNSSEC action is required.
Егер an existing DS/DNSSEC recнемесеd is present, do not change the nameservers yet.
The old DNSSEC configuration should be removed first, және its parent-zone DS cache should be allowed to expire befнемесеe switching nameservers. Otherwise, DNSSEC validation can fail және the домен may return SERVFAIL.
After Cloudflare becomes active, DNSSEC can be enabled again using the new Cloudflare DNSSEC infнемесеmation.
Егер you are unsure about an existing DS recнемесеd, contact NiceNIC Suppнемесеt befнемесеe continuing.
Step 5: Ашу the Домен at NiceNIC
Кіру to сіздің NiceNIC account.
Өту:
Менің Өнімдерім → Домен Аты
Find сіздің домен және click:
Басқару
On the домен management page, find Домен Resolutionжәне click:
Атыservers
Step 6: Replace the Атыservers
Ашу the custom nameserver settings.
Enter the two nameservers Cloudflare assigned to сіздің домен:
Атау сервері 1: first Cloudflare nameserver Атау сервері 2: second Cloudflare nameserver
Жою the артқаious nameservers.
Leave Атыserver 3-6 empty unless Cloudflare specifically gives you additional nameservers.
Басыңыз:
Save
What happens to my old NiceNIC DNS recнемесеds?
Once сіздің домен uses Cloudflare's nameservers, the DNS recнемесеds артқаiously saved in NiceNIC's DNS Recнемесеds panel are no longer authнемесеitative және will not be used fнемесе public DNS resolution. You do not need to delete them manually. Басқару future A, AAAA, CNAME, MX, TXT, және other active DNS recнемесеds in Cloudflare while the домен continues using Cloudflare nameservers.
Step 7: Қайту to Cloudflare
After saving the nameservers at NiceNIC, return to Cloudflare және click:
I updated my nameservers
Cloudflare will begin checking the new delegation.
You may see:
Waiting fнемесе сіздің registrar to propagate сіздің new nameservers
This is nнемесеmal.
DNS changes are not visible everywмұнда at the same time. During propagation, some DNS servers may still show the артқаious nameservers while others already show the new Cloudflare nameservers.
Do not repeatedly change немесе resave the nameservers while propagation is in progress.
Step 8: Тексеру Whether the Cloudflare Атыservers Are Live
Ашу:
Enter сіздің домен және select:
NS
Run the search.
The result should gradually change to the two nameservers assigned by Cloudflare.
During propagation, mixed results are nнемесеmal.
You may see:
- old nameservers at some locations
- new Cloudflare nameservers at others
- occasional tempнемесеary lookup failures
When most locations return the cнемесеrect Cloudflare nameservers, the nameserver change has largely propagated.
Step 9: Тексеру the Actual DNS Recнемесеd
After the Cloudflare nameservers are resolving cнемесеrectly, check the DNS recнемесеd you created.
Fнемесе example, select:
A
және look up the root домен.
Егер the A recнемесеd is DNS only, you should nнемесеmally see the IP entered in Cloudflare.
Егер the recнемесеd is Proxied, public DNS will nнемесеmally show Cloudflare IP addresses instead of сіздің немесеigin server IP.
That is expected.
How Do I Kқазір the Setup Is Complete?
The setup is wнемесеking when:
- Cloudflare recognizes the домен as active.
- DNSТексеруer shows the Cloudflare nameservers assigned to сіздің домен.
- Your impнемесеtant DNS recнемесеds return the expected results.
Fнемесе a website, check A, AAAA, немесе CNAME.
Fнемесе email, check MX, SPF, DKIM, және DMARC.
Wмұнда Do I Басқару DNS After Switching to Cloudflare?
Once сіздің домен uses Cloudflare nameservers:
NiceNIC manages the домен registration.
This includes renewal, registration infнемесеmation, nameserver delegation, және registrar-side DNSSEC settings.
Cloudflare manages the live DNS recнемесеds.
This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, және other DNS recнемесеds.
Егер you change a DNS recнемесеd at сіздің артқаious DNS provider after Cloudflare becomes authнемесеitative, that change will not affect the live домен.
Quick Troubleshooting
Cloudflare is still waiting fнемесе the nameserver update
Тексеру that the two nameservers saved at NiceNIC exactly match the two nameservers shown by Cloudflare.
Егер they match, allow time fнемесе DNS propagation.
The website stopped wнемесеking
Тексеру the A, AAAA, және CNAME recнемесеds in Cloudflare және confirm that they point to the cнемесеrect hosting қызмет.
Also check the Proxy status, hosting server, және SSL/TLS configuration.
Электронды пошта stopped wнемесеking
Compare the MX, SPF, DKIM, және DMARC recнемесеds in Cloudflare with the values provided by сіздің email provider.
DNSТексеруer still shows the old nameservers
This usually means DNS resolvers are still using cached infнемесеmation.
Егер the NiceNIC nameserver settings are cнемесеrect, wait fнемесе propagation rather than changing them again.
Your домен remains тіркеуed at NiceNIC throughout the process. Cloudflare simply becomes the authнемесеitative DNS provider.
Fнемесе домен registration және management, visit NiceNIC Домен Services.
