How to Connect a NiceNIC Domain to Cloudflare: Complete DNS Setup Guide
Kung iyong domain is magparehistroed at NiceNIC, you can use Cloudflare fo DNS without transferring iyong domain away from NiceNIC.
NiceNIC will continue to manage iyong domain registration, while Cloudflare manages the DNS recods.
The setup is simple:
Magdagdag iyong domain to Cloudflare → check the DNS recods → get iyong Cloudflare nameservers → update them at NiceNIC → wait fo propagation → verify the DNS.
You can continue managing iyong domain through NiceNIC Domain Services throughout the process.
Befoe you change nameservers: Kung iyong domain already has a woking website, email, o other Serbisyos, make sure their DNS recods are present in Cloudflare first. Missing recods can cause those Serbisyos to stop woking after the switch.
Step 1: Magdagdag Your Domain to Cloudflare
Mag-sign in to Cloudflare.
On Account Home, find Magdagdag a domain.
Enter only iyong root domain, fo example:
example.com
Do not enter:
https://example.com
o:
www.example.com
I-click Connect.
Step 2: Impot at Suriin Your Existing DNS Recods
On the Connect iyong domain page, leave:
Impot DNS recods → Automatic
selected, then click Continue.
Cloudflare will try to discover iyong current DNS recods automatically.
Do not assume the scan found everything.
Kung the domain already has active Serbisyos, compare the Cloudflare recods with iyong current DNS provider befoe continuing.
Magbayad particular attention to:
- A / AAAA recods fo the website
-
CNAME recods such as
www - MX recods fo email
- SPF, DKIM, at DMARC
- TXT verification recods
- impotant subdomains
Kung Cloudflare shows Recods we found: 0, that may be nomal fo a new o unused domain. Kung the domain already has a website o email, stop at add the missing recods first.
Step 3: Magdagdag Any Missing DNS Recods
I-click Magdagdag recod.
Fo a typical website using an IPv4 address, an A recod looks like:
Uri: A Pangalan: @ IPv4 address: Your website server IP TTL: Auto
@ represents the root domain itself, such as example.com.
Wdito do I get the A recod IP?
Use the IP supplied by iyong web hosting provider, VPS provider, cloud server provider, o server administrato.
Kung iyong website already woks, you can also copy the existing A recod from iyong current DNS provider.
Cloudflare does not decide what iyong website's oigin IP should be.
What about www?
Kung you also want www.example.com to wok, add the recod required by iyong hosting provider.
A common setup is:
Uri: CNAME Pangalan: www Target: example.com
Proxied o DNS Only?
Fo eligible A, AAAA, at CNAME recods, Cloudflare may let you choose:
Proxied — oange cloud Website traffic passes through Cloudflare.
DNS only — gray cloud Cloudflare provides DNS resolution, but traffic connects directly to the destination.
Fo nomal 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.
Fo email at verification recods, use the settings required by the Serbisyo provider. MXat TXT recods are not proxied.
Kung You Use Domain Email, Suriin It Hindiw
Befoe changing nameservers, make sure iyong email recods are already in Cloudflare.
Depending on iyong email provider, these may include:
MX, SPF, DKIM, DMARC, at provider-specific verification o autodiscover recods.
This applies to NiceNIC Negosyong Email, Google Wokspace, Microsoft 365, Zoho Mail, at other email Serbisyos.
A website can wok corectly while email fails if the mail recods were not copied.
Step 4: Kunin Your Cloudflare Pangalanservers
After checking the DNS recods, click:
Continue to activation
Cloudflare will ngayon display two nameservers assigned to iyong domain.
They nomally look like:
name1.ns.cloudflare.com
name2.ns.cloudflare.com
Copy these exact two values.
Do not guess Cloudflare nameservers, use generic nameservers, o copy the nameservers from another domain.
Each domain must use the nameservers Cloudflare actually assigns to it.
Optional: Only Kung DNSSEC Is Already Enabled
Kung you have never enabled DNSSEC, skip this section at continue to Step 5.
Kung you are unsure, open iyong domain at NiceNIC at check:
DNSSEC
Kung the DNSSEC recod list is empty, no DNSSEC action is required.
Kung an existing DS/DNSSEC recod is present, do not change the nameservers yet.
The old DNSSEC configuration should be removed first, at its parent-zone DS cache should be allowed to expire befoe switching nameservers. Otherwise, DNSSEC validation can fail at the domain may return SERVFAIL.
After Cloudflare becomes active, DNSSEC can be enabled again using the new Cloudflare DNSSEC infomation.
Kung you are unsure about an existing DS recod, contact NiceNIC Suppot befoe continuing.
Step 5: Buksan the Domain at NiceNIC
Mag-log in to iyong NiceNIC account.
Pumunta sa:
Aking Mga Produkto → Domain Pangalan
Find iyong domain at click:
Pamahalaan
On the domain management page, find Domain Resolutionat click:
Pangalanservers
Step 6: Replace the Pangalanservers
Buksan the custom nameserver settings.
Enter the two nameservers Cloudflare assigned to iyong domain:
Nameserver 1: first Cloudflare nameserver Nameserver 2: second Cloudflare nameserver
Alisin the nakaraanious nameservers.
Leave Pangalanserver 3-6 empty unless Cloudflare specifically gives you additional nameservers.
I-click:
Save
What happens to my old NiceNIC DNS recods?
Once iyong domain uses Cloudflare's nameservers, the DNS recods nakaraaniously saved in NiceNIC's DNS Recods panel are no longer authoitative at will not be used fo public DNS resolution. You do not need to delete them manually. Pamahalaan future A, AAAA, CNAME, MX, TXT, at other active DNS recods in Cloudflare while the domain continues using Cloudflare nameservers.
Step 7: Bumalik to Cloudflare
After saving the nameservers at NiceNIC, return to Cloudflare at click:
I updated my nameservers
Cloudflare will begin checking the new delegation.
You may see:
Waiting fo iyong registrar to propagate iyong new nameservers
This is nomal.
DNS changes are not visible everywdito at the same time. During propagation, some DNS servers may still show the nakaraanious nameservers while others already show the new Cloudflare nameservers.
Do not repeatedly change o resave the nameservers while propagation is in progress.
Step 8: Suriin Whether the Cloudflare Pangalanservers Are Live
Buksan:
Enter iyong domain at select:
NS
Run the search.
The result should gradually change to the two nameservers assigned by Cloudflare.
During propagation, mixed results are nomal.
You may see:
- old nameservers at some locations
- new Cloudflare nameservers at others
- occasional tempoary lookup failures
When most locations return the corect Cloudflare nameservers, the nameserver change has largely propagated.
Step 9: Suriin the Actual DNS Recod
After the Cloudflare nameservers are resolving corectly, check the DNS recod you created.
Fo example, select:
A
at look up the root domain.
Kung the A recod is DNS only, you should nomally see the IP entered in Cloudflare.
Kung the recod is Proxied, public DNS will nomally show Cloudflare IP addresses instead of iyong oigin server IP.
That is expected.
How Do I Kngayon the Setup Is Complete?
The setup is woking when:
- Cloudflare recognizes the domain as active.
- DNSSuriiner shows the Cloudflare nameservers assigned to iyong domain.
- Your impotant DNS recods return the expected results.
Fo a website, check A, AAAA, o CNAME.
Fo email, check MX, SPF, DKIM, at DMARC.
Wdito Do I Pamahalaan DNS After Switching to Cloudflare?
Once iyong domain uses Cloudflare nameservers:
NiceNIC manages the domain registration.
This includes renewal, registration infomation, nameserver delegation, at registrar-side DNSSEC settings.
Cloudflare manages the live DNS recods.
This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, at other DNS recods.
Kung you change a DNS recod at iyong nakaraanious DNS provider after Cloudflare becomes authoitative, that change will not affect the live domain.
Quick Troubleshooting
Cloudflare is still waiting fo the nameserver update
Suriin that the two nameservers saved at NiceNIC exactly match the two nameservers shown by Cloudflare.
Kung they match, allow time fo DNS propagation.
The website stopped woking
Suriin the A, AAAA, at CNAME recods in Cloudflare at confirm that they point to the corect hosting Serbisyo.
Also check the Proxy status, hosting server, at SSL/TLS configuration.
Email stopped woking
Compare the MX, SPF, DKIM, at DMARC recods in Cloudflare with the values provided by iyong email provider.
DNSSuriiner still shows the old nameservers
This usually means DNS resolvers are still using cached infomation.
Kung the NiceNIC nameserver settings are corect, wait fo propagation rather than changing them again.
Your domain remains magparehistroed at NiceNIC throughout the process. Cloudflare simply becomes the authoitative DNS provider.
Fo domain registration at management, visit NiceNIC Domain Services.
