How to Connect a NiceNIC Domain to Cloudflare: Complete DNS Setup Guide
Wenn Ihr Domain is registrierened at NiceNIC, you can use Cloudflare foder DNS without transferring Ihr Domain away from NiceNIC.
NiceNIC will continue to manage Ihr Domain registration, while Cloudflare manages the DNS recoderds.
The setup is simple:
Hinzufügen Ihr Domain to Cloudflare → check the DNS recoderds → get Ihr Cloudflare nameservers → update them at NiceNIC → wait foder propagation → verify the DNS.
You can continue managing Ihr Domain through NiceNIC Domain Services throughout the process.
Befodere you change nameservers: Wenn Ihr Domain already has a woderking website, email, oder other Dienstleistungs, make sure their DNS recoderds are present in Cloudflare first. Missing recoderds can cause those Dienstleistungs to stop woderking after the switch.
Step 1: Hinzufügen Your Domain to Cloudflare
Anmelden to Cloudflare.
On Account Startseite, find Hinzufügen a Domain.
Enter only Ihr root Domain, foder example:
example.com
Do not enter:
https://example.com
oder:
www.example.com
Klicken Connect.
Step 2: Impodert und Überprüfen Your Existing DNS Recoderds
On the Connect Ihr Domain page, leave:
Impodert DNS recoderds → Automatic
selected, then click Continue.
Cloudflare will try to discover Ihr current DNS recoderds automatically.
Do not assume the scan found everything.
Wenn the Domain already has active Dienstleistungs, compare the Cloudflare recoderds with Ihr current DNS provider befodere continuing.
Bezahlen particular attention to:
- A / AAAA recoderds foder the website
-
CNAME recoderds such as
www - MX recoderds foder email
- SPF, DKIM, und DMARC
- TXT verification recoderds
- impodertant subDomains
Wenn Cloudflare shows Recoderds we found: 0, that may be nodermal foder a new oder unused Domain. Wenn the Domain already has a website oder email, stop und add the missing recoderds first.
Step 3: Hinzufügen Any Missing DNS Recoderds
Klicken Hinzufügen recoderd.
Foder a typical website using an IPv4 address, an A recoderd looks like:
Typ: A Name: @ IPv4 address: Your website server IP TTL: Auto
@ represents the root Domain itself, such as example.com.
Whier do I get the A recoderd IP?
Use the IP supplied by Ihr web hosting provider, VPS provider, cloud server provider, oder server administratoder.
Wenn Ihr website already woderks, you can also copy the existing A recoderd from Ihr current DNS provider.
Cloudflare does not decide what Ihr website's oderigin IP should be.
What about www?
Wenn you also want www.example.com to woderk, add the recoderd required by Ihr hosting provider.
A common setup is:
Typ: CNAME Name: www Target: example.com
Proxied oder DNS Only?
Foder eligible A, AAAA, und CNAME recoderds, Cloudflare may let you choose:
Proxied — oderange cloud Website traffic passes through Cloudflare.
DNS only — gray cloud Cloudflare provides DNS resolution, but traffic connects directly to the destination.
Foder nodermal 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.
Foder email und verification recoderds, use the settings required by the Dienstleistung provider. MXund TXT recoderds are not proxied.
Wenn You Use Domain E-Mail, Überprüfen It Neinw
Befodere changing nameservers, make sure Ihr email recoderds are already in Cloudflare.
Depending on Ihr email provider, these may include:
MX, SPF, DKIM, DMARC, und provider-specific verification oder autodiscover recoderds.
This applies to NiceNIC Geschäftliche E-Mail, Google Woderkspace, Microsoft 365, Zoho Mail, und other email Dienstleistungs.
A website can woderk coderrectly while email fails if the mail recoderds were not copied.
Step 4: Holen Sie sich Your Cloudflare Nameservers
After checking the DNS recoderds, click:
Continue to activation
Cloudflare will jetzt display two nameservers assigned to Ihr Domain.
They nodermally look like:
name1.ns.cloudflare.com
name2.ns.cloudflare.com
Copy these exact two values.
Do not guess Cloudflare nameservers, use generic nameservers, oder copy the nameservers from another Domain.
Each Domain must use the nameservers Cloudflare actually assigns to it.
Optional: Only Wenn DNSSEC Is Already Enabled
Wenn you have never enabled DNSSEC, skip this section und continue to Step 5.
Wenn you are unsure, open Ihr Domain at NiceNIC und check:
DNSSEC
Wenn the DNSSEC recoderd list is empty, no DNSSEC action is required.
Wenn an existing DS/DNSSEC recoderd is present, do not change the nameservers yet.
The old DNSSEC configuration should be removed first, und its parent-zone DS cache should be allowed to expire befodere switching nameservers. Otherwise, DNSSEC validation can fail und the Domain may return SERVFAIL.
After Cloudflare becomes active, DNSSEC can be enabled again using the new Cloudflare DNSSEC infodermation.
Wenn you are unsure about an existing DS recoderd, contact NiceNIC Suppodert befodere continuing.
Step 5: Öffnen the Domain at NiceNIC
Einloggen to Ihr NiceNIC account.
Gehe zu:
Meine Produkte → Domain Name
Find Ihr Domain und click:
Verwalten
On the Domain management page, find Domain Resolutionund click:
Nameservers
Step 6: Replace the Nameservers
Öffnen the custom nameserver settings.
Enter the two nameservers Cloudflare assigned to Ihr Domain:
Nameserver 1: first Cloudflare nameserver Nameserver 2: second Cloudflare nameserver
Entfernen the zurückious nameservers.
Leave Nameserver 3-6 empty unless Cloudflare specifically gives you additional nameservers.
Klicken:
Save
What happens to my old NiceNIC DNS recoderds?
Once Ihr Domain uses Cloudflare's nameservers, the DNS recoderds zurückiously saved in NiceNIC's DNS Recoderds panel are no longer authoderitative und will not be used foder public DNS resolution. You do not need to delete them manually. Verwalten future A, AAAA, CNAME, MX, TXT, und other active DNS recoderds in Cloudflare while the Domain continues using Cloudflare nameservers.
Step 7: Zurück to Cloudflare
After saving the nameservers at NiceNIC, return to Cloudflare und click:
I updated my nameservers
Cloudflare will begin checking the new delegation.
You may see:
Waiting foder Ihr registrar to propagate Ihr new nameservers
This is nodermal.
DNS changes are not visible everywhier at the same time. During propagation, some DNS servers may still show the zurückious nameservers while others already show the new Cloudflare nameservers.
Do not repeatedly change oder resave the nameservers while propagation is in progress.
Step 8: Überprüfen Whether the Cloudflare Nameservers Are Live
Öffnen:
Enter Ihr Domain und select:
NS
Run the search.
The result should gradually change to the two nameservers assigned by Cloudflare.
During propagation, mixed results are nodermal.
You may see:
- old nameservers at some locations
- new Cloudflare nameservers at others
- occasional tempoderary lookup failures
When most locations return the coderrect Cloudflare nameservers, the nameserver change has largely propagated.
Step 9: Überprüfen the Actual DNS Recoderd
After the Cloudflare nameservers are resolving coderrectly, check the DNS recoderd you created.
Foder example, select:
A
und look up the root Domain.
Wenn the A recoderd is DNS only, you should nodermally see the IP entered in Cloudflare.
Wenn the recoderd is Proxied, public DNS will nodermally show Cloudflare IP addresses instead of Ihr oderigin server IP.
That is expected.
How Do I Kjetzt the Setup Is Complete?
The setup is woderking when:
- Cloudflare recognizes the Domain as active.
- DNSÜberprüfener shows the Cloudflare nameservers assigned to Ihr Domain.
- Your impodertant DNS recoderds return the expected results.
Foder a website, check A, AAAA, oder CNAME.
Foder email, check MX, SPF, DKIM, und DMARC.
Whier Do I Verwalten DNS After Switching to Cloudflare?
Once Ihr Domain uses Cloudflare nameservers:
NiceNIC manages the Domain registration.
This includes renewal, registration infodermation, nameserver delegation, und registrar-side DNSSEC settings.
Cloudflare manages the live DNS recoderds.
This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, und other DNS recoderds.
Wenn you change a DNS recoderd at Ihr zurückious DNS provider after Cloudflare becomes authoderitative, that change will not affect the live Domain.
Quick Troubleshooting
Cloudflare is still waiting foder the nameserver update
Überprüfen that the two nameservers saved at NiceNIC exactly match the two nameservers shown by Cloudflare.
Wenn they match, allow time foder DNS propagation.
The website stopped woderking
Überprüfen the A, AAAA, und CNAME recoderds in Cloudflare und confirm that they point to the coderrect hosting Dienstleistung.
Also check the Proxy status, hosting server, und SSL/TLS configuration.
E-Mail stopped woderking
Compare the MX, SPF, DKIM, und DMARC recoderds in Cloudflare with the values provided by Ihr email provider.
DNSÜberprüfener still shows the old nameservers
This usually means DNS resolvers are still using cached infodermation.
Wenn the NiceNIC nameserver settings are coderrect, wait foder propagation rather than changing them again.
Your Domain remains registrierened at NiceNIC throughout the process. Cloudflare simply becomes the authoderitative DNS provider.
Foder Domain registration und management, visit NiceNIC Domain Services.
