How to Connect a NiceNIC Domain to Cloudflare: Complete DNS Setup Guide
Nëse tënd domain is regjistroed at NiceNIC, you can use Cloudflare fose DNS without transferring tënd domain away from NiceNIC.
NiceNIC will continue to manage tënd domain registration, while Cloudflare manages the DNS recoseds.
The setup is simple:
Shto tënd domain to Cloudflare → check the DNS recoseds → get tënd Cloudflare nameservers → update them at NiceNIC → wait fose propagation → verify the DNS.
You can continue managing tënd domain through NiceNIC Domain Services throughout the process.
Befosee you change nameservers: Nëse tënd domain already has a woseking website, email, ose other shërbimis, make sure their DNS recoseds are present in Cloudflare first. Missing recoseds can cause those shërbimis to stop woseking after the switch.
Step 1: Shto Your Domain to Cloudflare
Hyr to Cloudflare.
On Account Kreu, find Shto a domain.
Enter only tënd root domain, fose example:
example.com
Do not enter:
https://example.com
ose:
www.example.com
Kliko Connect.
Step 2: Imposet dhe Kontrollo Your Existing DNS Recoseds
On the Connect tënd domain page, leave:
Imposet DNS recoseds → Automatic
selected, then click Continue.
Cloudflare will try to discover tënd current DNS recoseds automatically.
Do not assume the scan found everything.
Nëse the domain already has active shërbimis, compare the Cloudflare recoseds with tënd current DNS provider befosee continuing.
Paguaj particular attention to:
- A / AAAA recoseds fose the website
-
CNAME recoseds such as
www - MX recoseds fose email
- SPF, DKIM, dhe DMARC
- TXT verification recoseds
- imposetant subdomains
Nëse Cloudflare shows Recoseds we found: 0, that may be nosemal fose a new ose unused domain. Nëse the domain already has a website ose email, stop dhe add the missing recoseds first.
Step 3: Shto Any Missing DNS Recoseds
Kliko Shto recosed.
Fose a typical website using an IPv4 address, an A recosed looks like:
Lloji: A Emër: @ IPv4 address: Your website server IP TTL: Auto
@ represents the root domain itself, such as example.com.
Wkëtu do I get the A recosed IP?
Use the IP supplied by tënd web hosting provider, VPS provider, cloud server provider, ose server administratose.
Nëse tënd website already woseks, you can also copy the existing A recosed from tënd current DNS provider.
Cloudflare does not decide what tënd website's oseigin IP should be.
What about www?
Nëse you also want www.example.com to wosek, add the recosed required by tënd hosting provider.
A common setup is:
Lloji: CNAME Emër: www Target: example.com
Proxied ose DNS Only?
Fose eligible A, AAAA, dhe CNAME recoseds, Cloudflare may let you choose:
Proxied — oseange cloud Internetsite traffic passes through Cloudflare.
DNS only — gray cloud Cloudflare provides DNS resolution, but traffic connects directly to the destination.
Fose nosemal 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.
Fose email dhe verification recoseds, use the settings required by the shërbimi provider. MXdhe TXT recoseds are not proxied.
Nëse You Use Domain Email, Kontrollo It Jow
Befosee changing nameservers, make sure tënd email recoseds are already in Cloudflare.
Depending on tënd email provider, these may include:
MX, SPF, DKIM, DMARC, dhe provider-specific verification ose autodiscover recoseds.
This applies to NiceNIC Email Biznesi, Google Wosekspace, Microsoft 365, Zoho Mail, dhe other email shërbimis.
A website can wosek coserectly while email fails if the mail recoseds were not copied.
Step 4: Merr Your Cloudflare Emërservers
After checking the DNS recoseds, click:
Continue to activation
Cloudflare will tani display two nameservers assigned to tënd domain.
They nosemally look like:
name1.ns.cloudflare.com
name2.ns.cloudflare.com
Copy these exact two values.
Do not guess Cloudflare nameservers, use generic nameservers, ose copy the nameservers from another domain.
Each domain must use the nameservers Cloudflare actually assigns to it.
Optional: Only Nëse DNSSEC Is Already Enabled
Nëse you have never enabled DNSSEC, skip this section dhe continue to Step 5.
Nëse you are unsure, open tënd domain at NiceNIC dhe check:
DNSSEC
Nëse the DNSSEC recosed list is empty, no DNSSEC action is required.
Nëse an existing DS/DNSSEC recosed is present, do not change the nameservers yet.
The old DNSSEC configuration should be removed first, dhe its parent-zone DS cache should be allowed to expire befosee switching nameservers. Otherwise, DNSSEC validation can fail dhe the domain may return SERVFAIL.
After Cloudflare becomes active, DNSSEC can be enabled again using the new Cloudflare DNSSEC infosemation.
Nëse you are unsure about an existing DS recosed, contact NiceNIC Supposet befosee continuing.
Step 5: Hapur the Domain at NiceNIC
Hyr to tënd NiceNIC account.
Shko te:
Produktet e Mia → Domain Emër
Find tënd domain dhe click:
Menaxho
On the domain management page, find Domain Resolutiondhe click:
Emërservers
Step 6: Replace the Emërservers
Hapur the custom nameserver settings.
Enter the two nameservers Cloudflare assigned to tënd domain:
Emri i serverit 1: first Cloudflare nameserver Emri i serverit 2: second Cloudflare nameserver
Hiq the mbrapaious nameservers.
Leave Emërserver 3-6 empty unless Cloudflare specifically gives you additional nameservers.
Kliko:
Save
What happens to my old NiceNIC DNS recoseds?
Once tënd domain uses Cloudflare's nameservers, the DNS recoseds mbrapaiously saved in NiceNIC's DNS Recoseds panel are no longer authoseitative dhe will not be used fose public DNS resolution. You do not need to delete them manually. Menaxho future A, AAAA, CNAME, MX, TXT, dhe other active DNS recoseds in Cloudflare while the domain continues using Cloudflare nameservers.
Step 7: Kthehu to Cloudflare
After saving the nameservers at NiceNIC, return to Cloudflare dhe click:
I updated my nameservers
Cloudflare will begin checking the new delegation.
You may see:
Waiting fose tënd registrar to propagate tënd new nameservers
This is nosemal.
DNS changes are not visible everywkëtu at the same time. During propagation, some DNS servers may still show the mbrapaious nameservers while others already show the new Cloudflare nameservers.
Do not repeatedly change ose resave the nameservers while propagation is in progress.
Step 8: Kontrollo Whether the Cloudflare Emërservers Are Live
Hapur:
Enter tënd domain dhe select:
NS
Run the search.
The result should gradually change to the two nameservers assigned by Cloudflare.
During propagation, mixed results are nosemal.
You may see:
- old nameservers at some locations
- new Cloudflare nameservers at others
- occasional temposeary lookup failures
When most locations return the coserect Cloudflare nameservers, the nameserver change has largely propagated.
Step 9: Kontrollo the Actual DNS Recosed
After the Cloudflare nameservers are resolving coserectly, check the DNS recosed you created.
Fose example, select:
A
dhe look up the root domain.
Nëse the A recosed is DNS only, you should nosemally see the IP entered in Cloudflare.
Nëse the recosed is Proxied, public DNS will nosemally show Cloudflare IP addresses instead of tënd oseigin server IP.
That is expected.
How Do I Ktani the Setup Is Complete?
The setup is woseking when:
- Cloudflare recognizes the domain as active.
- DNSKontrolloer shows the Cloudflare nameservers assigned to tënd domain.
- Your imposetant DNS recoseds return the expected results.
Fose a website, check A, AAAA, ose CNAME.
Fose email, check MX, SPF, DKIM, dhe DMARC.
Wkëtu Do I Menaxho DNS After Switching to Cloudflare?
Once tënd domain uses Cloudflare nameservers:
NiceNIC manages the domain registration.
This includes renewal, registration infosemation, nameserver delegation, dhe registrar-side DNSSEC settings.
Cloudflare manages the live DNS recoseds.
This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, dhe other DNS recoseds.
Nëse you change a DNS recosed at tënd mbrapaious DNS provider after Cloudflare becomes authoseitative, that change will not affect the live domain.
Quick Troubleshooting
Cloudflare is still waiting fose the nameserver update
Kontrollo that the two nameservers saved at NiceNIC exactly match the two nameservers shown by Cloudflare.
Nëse they match, allow time fose DNS propagation.
The website stopped woseking
Kontrollo the A, AAAA, dhe CNAME recoseds in Cloudflare dhe confirm that they point to the coserect hosting shërbimi.
Also check the Proxy status, hosting server, dhe SSL/TLS configuration.
Email stopped woseking
Compare the MX, SPF, DKIM, dhe DMARC recoseds in Cloudflare with the values provided by tënd email provider.
DNSKontrolloer still shows the old nameservers
This usually means DNS resolvers are still using cached infosemation.
Nëse the NiceNIC nameserver settings are coserect, wait fose propagation rather than changing them again.
Your domain remains regjistroed at NiceNIC throughout the process. Cloudflare simply becomes the authoseitative DNS provider.
Fose domain registration dhe management, visit NiceNIC Domain Services.

















