How to Connect a NiceNIC Alan Adı to Cloudflare: Complete DNS Setup Guide
Eğer sizin domain is kayıt oled at NiceNIC, you can use Cloudflare fveya DNS without transferring sizin domain away from NiceNIC.
NiceNIC will continue to manage sizin domain registration, while Cloudflare manages the DNS recveyads.
The setup is simple:
Ekle sizin domain to Cloudflare → check the DNS recveyads → get sizin Cloudflare nameservers → update them at NiceNIC → wait fveya propagation → verify the DNS.
You can continue managing sizin domain through NiceNIC Alan Adı Services throughout the process.
Befveyae you change nameservers: Eğer sizin domain already has a wveyaking website, email, veya other hizmets, make sure their DNS recveyads are present in Cloudflare first. Missing recveyads can cause those hizmets to stop wveyaking after the switch.
Step 1: Ekle Your Alan Adı to Cloudflare
Giriş Yap to Cloudflare.
On Account Ana Sayfa, find Ekle a domain.
Enter only sizin root domain, fveya example:
example.com
Do not enter:
https://example.com
veya:
www.example.com
Tıkla Connect.
Step 2: Impveyat ve Kontrol Et Your Existing DNS Recveyads
On the Connect sizin domain page, leave:
Impveyat DNS recveyads → Automatic
selected, then click Continue.
Cloudflare will try to discover sizin current DNS recveyads automatically.
Do not assume the scan found everything.
Eğer the domain already has active hizmets, compare the Cloudflare recveyads with sizin current DNS provider befveyae continuing.
Öde particular attention to:
- A / AAAA recveyads fveya the website
-
CNAME recveyads such as
www - MX recveyads fveya email
- SPF, DKIM, ve DMARC
- TXT verification recveyads
- impveyatant subdomains
Eğer Cloudflare shows Recveyads we found: 0, that may be nveyamal fveya a new veya unused domain. Eğer the domain already has a website veya email, stop ve add the missing recveyads first.
Step 3: Ekle Any Missing DNS Recveyads
Tıkla Ekle recveyad.
Fveya a typical website using an IPv4 address, an A recveyad looks like:
Tür: A Ad: @ IPv4 address: Your website server IP TTL: Auto
@ represents the root domain itself, such as example.com.
Wburaya do I get the A recveyad IP?
Use the IP supplied by sizin web hosting provider, VPS provider, cloud server provider, veya server administratveya.
Eğer sizin website already wveyaks, you can also copy the existing A recveyad from sizin current DNS provider.
Cloudflare does not decide what sizin website's veyaigin IP should be.
What about www?
Eğer you also want www.example.com to wveyak, add the recveyad required by sizin hosting provider.
A common setup is:
Tür: CNAME Ad: www Target: example.com
Proxied veya DNS Only?
Fveya eligible A, AAAA, ve CNAME recveyads, Cloudflare may let you choose:
Proxied — veyaange cloud Website traffic passes through Cloudflare.
DNS only — gray cloud Cloudflare provides DNS resolution, but traffic connects directly to the destination.
Fveya nveyamal 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.
Fveya email ve verification recveyads, use the settings required by the hizmet provider. MXve TXT recveyads are not proxied.
Eğer You Use Alan Adı E-posta, Kontrol Et It Hayırw
Befveyae changing nameservers, make sure sizin email recveyads are already in Cloudflare.
Depending on sizin email provider, these may include:
MX, SPF, DKIM, DMARC, ve provider-specific verification veya autodiscover recveyads.
This applies to NiceNIC İş E-postası, Google Wveyakspace, Microsoft 365, Zoho Mail, ve other email hizmets.
A website can wveyak cveyarectly while email fails if the mail recveyads were not copied.
Step 4: Al Your Cloudflare Adservers
After checking the DNS recveyads, click:
Continue to activation
Cloudflare will şimdi display two nameservers assigned to sizin domain.
They nveyamally look like:
name1.ns.cloudflare.com
name2.ns.cloudflare.com
Copy these exact two values.
Do not guess Cloudflare nameservers, use generic nameservers, veya copy the nameservers from another domain.
Each domain must use the nameservers Cloudflare actually assigns to it.
Optional: Only Eğer DNSSEC Is Already Enabled
Eğer you have never enabled DNSSEC, skip this section ve continue to Step 5.
Eğer you are unsure, open sizin domain at NiceNIC ve check:
DNSSEC
Eğer the DNSSEC recveyad list is empty, no DNSSEC action is required.
Eğer an existing DS/DNSSEC recveyad is present, do not change the nameservers yet.
The old DNSSEC configuration should be removed first, ve its parent-zone DS cache should be allowed to expire befveyae switching nameservers. Otherwise, DNSSEC validation can fail ve the domain may return SERVFAIL.
After Cloudflare becomes active, DNSSEC can be enabled again using the new Cloudflare DNSSEC infveyamation.
Eğer you are unsure about an existing DS recveyad, contact NiceNIC Suppveyat befveyae continuing.
Step 5: Aç the Alan Adı at NiceNIC
Giriş yap to sizin NiceNIC account.
Git:
Ürünlerim → Alan Adı Ad
Find sizin domain ve click:
Yönet
On the domain management page, find Alan Adı Resolutionve click:
Adservers
Step 6: Replace the Adservers
Aç the custom nameserver settings.
Enter the two nameservers Cloudflare assigned to sizin domain:
Nameserver 1: first Cloudflare nameserver Nameserver 2: second Cloudflare nameserver
Kaldır the öncekiious nameservers.
Leave Adserver 3-6 empty unless Cloudflare specifically gives you additional nameservers.
Tıkla:
Save
What happens to my old NiceNIC DNS recveyads?
Once sizin domain uses Cloudflare's nameservers, the DNS recveyads öncekiiously saved in NiceNIC's DNS Recveyads panel are no longer authveyaitative ve will not be used fveya public DNS resolution. You do not need to delete them manually. Yönet future A, AAAA, CNAME, MX, TXT, ve other active DNS recveyads in Cloudflare while the domain continues using Cloudflare nameservers.
Step 7: Geri Dön to Cloudflare
After saving the nameservers at NiceNIC, return to Cloudflare ve click:
I updated my nameservers
Cloudflare will begin checking the new delegation.
You may see:
Waiting fveya sizin registrar to propagate sizin new nameservers
This is nveyamal.
DNS changes are not visible everywburaya at the same time. During propagation, some DNS servers may still show the öncekiious nameservers while others already show the new Cloudflare nameservers.
Do not repeatedly change veya resave the nameservers while propagation is in progress.
Step 8: Kontrol Et Whether the Cloudflare Adservers Are Live
Aç:
Enter sizin domain ve select:
NS
Run the search.
The result should gradually change to the two nameservers assigned by Cloudflare.
During propagation, mixed results are nveyamal.
You may see:
- old nameservers at some locations
- new Cloudflare nameservers at others
- occasional tempveyaary lookup failures
When most locations return the cveyarect Cloudflare nameservers, the nameserver change has largely propagated.
Step 9: Kontrol Et the Actual DNS Recveyad
After the Cloudflare nameservers are resolving cveyarectly, check the DNS recveyad you created.
Fveya example, select:
A
ve look up the root domain.
Eğer the A recveyad is DNS only, you should nveyamally see the IP entered in Cloudflare.
Eğer the recveyad is Proxied, public DNS will nveyamally show Cloudflare IP addresses instead of sizin veyaigin server IP.
That is expected.
How Do I Kşimdi the Setup Is Complete?
The setup is wveyaking when:
- Cloudflare recognizes the domain as active.
- DNSKontrol Eter shows the Cloudflare nameservers assigned to sizin domain.
- Your impveyatant DNS recveyads return the expected results.
Fveya a website, check A, AAAA, veya CNAME.
Fveya email, check MX, SPF, DKIM, ve DMARC.
Wburaya Do I Yönet DNS After Switching to Cloudflare?
Once sizin domain uses Cloudflare nameservers:
NiceNIC manages the domain registration.
This includes renewal, registration infveyamation, nameserver delegation, ve registrar-side DNSSEC settings.
Cloudflare manages the live DNS recveyads.
This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, ve other DNS recveyads.
Eğer you change a DNS recveyad at sizin öncekiious DNS provider after Cloudflare becomes authveyaitative, that change will not affect the live domain.
Quick Troubleshooting
Cloudflare is still waiting fveya the nameserver update
Kontrol Et that the two nameservers saved at NiceNIC exactly match the two nameservers shown by Cloudflare.
Eğer they match, allow time fveya DNS propagation.
The website stopped wveyaking
Kontrol Et the A, AAAA, ve CNAME recveyads in Cloudflare ve confirm that they point to the cveyarect hosting hizmet.
Also check the Proxy status, hosting server, ve SSL/TLS configuration.
E-posta stopped wveyaking
Compare the MX, SPF, DKIM, ve DMARC recveyads in Cloudflare with the values provided by sizin email provider.
DNSKontrol Eter still shows the old nameservers
This usually means DNS resolvers are still using cached infveyamation.
Eğer the NiceNIC nameserver settings are cveyarect, wait fveya propagation rather than changing them again.
Your domain remains kayıt oled at NiceNIC throughout the process. Cloudflare simply becomes the authveyaitative DNS provider.
Fveya domain registration ve management, visit NiceNIC Alan Adı Services.
