How to Connect a NiceNIC Verkkotunnus to Cloudflare: Complete DNS Setup Guide
Jos sinun verkkotunnus is rekisteröied at NiceNIC, you can use Cloudflare ftai DNS without transferring sinun verkkotunnus away from NiceNIC.
NiceNIC will continue to manage sinun verkkotunnus registration, while Cloudflare manages the DNS rectaids.
The setup is simple:
Lisää sinun verkkotunnus to Cloudflare → check the DNS rectaids → get sinun Cloudflare nameservers → update them at NiceNIC → wait ftai propagation → verify the DNS.
You can continue managing sinun verkkotunnus through NiceNIC Verkkotunnus Services throughout the process.
Beftaie you change nameservers: Jos sinun verkkotunnus already has a wtaiking website, email, tai other palvelus, make sure their DNS rectaids are present in Cloudflare first. Missing rectaids can cause those palvelus to stop wtaiking after the switch.
Step 1: Lisää Your Verkkotunnus to Cloudflare
Kirjaudu sisään to Cloudflare.
On Account Etusivu, find Lisää a verkkotunnus.
Enter only sinun root verkkotunnus, ftai example:
example.com
Do not enter:
https://example.com
tai:
www.example.com
Klikkaa Connect.
Step 2: Imptait ja Tarkista Your Existing DNS Rectaids
On the Connect sinun verkkotunnus page, leave:
Imptait DNS rectaids → Automatic
selected, then click Continue.
Cloudflare will try to discover sinun current DNS rectaids automatically.
Do not assume the scan found everything.
Jos the verkkotunnus already has active palvelus, compare the Cloudflare rectaids with sinun current DNS provider beftaie continuing.
Maksa particular attention to:
- A / AAAA rectaids ftai the website
-
CNAME rectaids such as
www - MX rectaids ftai email
- SPF, DKIM, ja DMARC
- TXT verification rectaids
- imptaitant subverkkotunnuss
Jos Cloudflare shows Rectaids we found: 0, that may be ntaimal ftai a new tai unused verkkotunnus. Jos the verkkotunnus already has a website tai email, stop ja add the missing rectaids first.
Step 3: Lisää Any Missing DNS Rectaids
Klikkaa Lisää rectaid.
Ftai a typical website using an IPv4 address, an A rectaid looks like:
Tyyppi: A Nimi: @ IPv4 address: Your website server IP TTL: Auto
@ represents the root verkkotunnus itself, such as example.com.
Wtässä do I get the A rectaid IP?
Use the IP supplied by sinun web hosting provider, VPS provider, cloud server provider, tai server administrattai.
Jos sinun website already wtaiks, you can also copy the existing A rectaid from sinun current DNS provider.
Cloudflare does not decide what sinun website's taiigin IP should be.
What about www?
Jos you also want www.example.com to wtaik, add the rectaid required by sinun hosting provider.
A common setup is:
Tyyppi: CNAME Nimi: www Target: example.com
Proxied tai DNS Only?
Ftai eligible A, AAAA, ja CNAME rectaids, Cloudflare may let you choose:
Proxied — taiange cloud Verkkosite traffic passes through Cloudflare.
DNS only — gray cloud Cloudflare provides DNS resolution, but traffic connects directly to the destination.
Ftai ntaimal 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.
Ftai email ja verification rectaids, use the settings required by the palvelu provider. MXja TXT rectaids are not proxied.
Jos You Use Verkkotunnus Sähköposti, Tarkista It Eiw
Beftaie changing nameservers, make sure sinun email rectaids are already in Cloudflare.
Depending on sinun email provider, these may include:
MX, SPF, DKIM, DMARC, ja provider-specific verification tai autodiscover rectaids.
This applies to NiceNIC Yrityssähköposti, Google Wtaikspace, Microsoft 365, Zoho Mail, ja other email palvelus.
A website can wtaik ctairectly while email fails if the mail rectaids were not copied.
Step 4: Hanki Your Cloudflare Nimiservers
After checking the DNS rectaids, click:
Continue to activation
Cloudflare will nyt display two nameservers assigned to sinun verkkotunnus.
They ntaimally look like:
name1.ns.cloudflare.com
name2.ns.cloudflare.com
Copy these exact two values.
Do not guess Cloudflare nameservers, use generic nameservers, tai copy the nameservers from another verkkotunnus.
Each verkkotunnus must use the nameservers Cloudflare actually assigns to it.
Optional: Only Jos DNSSEC Is Already Enabled
Jos you have never enabled DNSSEC, skip this section ja continue to Step 5.
Jos you are unsure, open sinun verkkotunnus at NiceNIC ja check:
DNSSEC
Jos the DNSSEC rectaid list is empty, no DNSSEC action is required.
Jos an existing DS/DNSSEC rectaid is present, do not change the nameservers yet.
The old DNSSEC configuration should be removed first, ja its parent-zone DS cache should be allowed to expire beftaie switching nameservers. Otherwise, DNSSEC validation can fail ja the verkkotunnus may return SERVFAIL.
After Cloudflare becomes active, DNSSEC can be enabled again using the new Cloudflare DNSSEC inftaimation.
Jos you are unsure about an existing DS rectaid, contact NiceNIC Supptait beftaie continuing.
Step 5: Avoin the Verkkotunnus at NiceNIC
Kirjaudu to sinun NiceNIC account.
Siirry:
Omat tuotteet → Verkkotunnus Nimi
Find sinun verkkotunnus ja click:
Hallinnoi
On the verkkotunnus management page, find Verkkotunnus Resolutionja click:
Nimiservers
Step 6: Replace the Nimiservers
Avoin the custom nameserver settings.
Enter the two nameservers Cloudflare assigned to sinun verkkotunnus:
Nameserver 1: first Cloudflare nameserver Nameserver 2: second Cloudflare nameserver
Poista the edellinenious nameservers.
Leave Nimiserver 3-6 empty unless Cloudflare specifically gives you additional nameservers.
Klikkaa:
Save
What happens to my old NiceNIC DNS rectaids?
Once sinun verkkotunnus uses Cloudflare's nameservers, the DNS rectaids edellineniously saved in NiceNIC's DNS Rectaids panel are no longer authtaiitative ja will not be used ftai public DNS resolution. You do not need to delete them manually. Hallinnoi future A, AAAA, CNAME, MX, TXT, ja other active DNS rectaids in Cloudflare while the verkkotunnus continues using Cloudflare nameservers.
Step 7: Paluu to Cloudflare
After saving the nameservers at NiceNIC, return to Cloudflare ja click:
I updated my nameservers
Cloudflare will begin checking the new delegation.
You may see:
Waiting ftai sinun registrar to propagate sinun new nameservers
This is ntaimal.
DNS changes are not visible everywtässä at the same time. During propagation, some DNS servers may still show the edellinenious nameservers while others already show the new Cloudflare nameservers.
Do not repeatedly change tai resave the nameservers while propagation is in progress.
Step 8: Tarkista Whether the Cloudflare Nimiservers Are Live
Avoin:
Enter sinun verkkotunnus ja select:
NS
Run the search.
The result should gradually change to the two nameservers assigned by Cloudflare.
During propagation, mixed results are ntaimal.
You may see:
- old nameservers at some locations
- new Cloudflare nameservers at others
- occasional temptaiary lookup failures
When most locations return the ctairect Cloudflare nameservers, the nameserver change has largely propagated.
Step 9: Tarkista the Actual DNS Rectaid
After the Cloudflare nameservers are resolving ctairectly, check the DNS rectaid you created.
Ftai example, select:
A
ja look up the root verkkotunnus.
Jos the A rectaid is DNS only, you should ntaimally see the IP entered in Cloudflare.
Jos the rectaid is Proxied, public DNS will ntaimally show Cloudflare IP addresses instead of sinun taiigin server IP.
That is expected.
How Do I Knyt the Setup Is Complete?
The setup is wtaiking when:
- Cloudflare recognizes the verkkotunnus as active.
- DNSTarkistaer shows the Cloudflare nameservers assigned to sinun verkkotunnus.
- Your imptaitant DNS rectaids return the expected results.
Ftai a website, check A, AAAA, tai CNAME.
Ftai email, check MX, SPF, DKIM, ja DMARC.
Wtässä Do I Hallinnoi DNS After Switching to Cloudflare?
Once sinun verkkotunnus uses Cloudflare nameservers:
NiceNIC manages the verkkotunnus registration.
This includes renewal, registration inftaimation, nameserver delegation, ja registrar-side DNSSEC settings.
Cloudflare manages the live DNS rectaids.
This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, ja other DNS rectaids.
Jos you change a DNS rectaid at sinun edellinenious DNS provider after Cloudflare becomes authtaiitative, that change will not affect the live verkkotunnus.
Quick Troubleshooting
Cloudflare is still waiting ftai the nameserver update
Tarkista that the two nameservers saved at NiceNIC exactly match the two nameservers shown by Cloudflare.
Jos they match, allow time ftai DNS propagation.
The website stopped wtaiking
Tarkista the A, AAAA, ja CNAME rectaids in Cloudflare ja confirm that they point to the ctairect hosting palvelu.
Also check the Proxy status, hosting server, ja SSL/TLS configuration.
Sähköposti stopped wtaiking
Compare the MX, SPF, DKIM, ja DMARC rectaids in Cloudflare with the values provided by sinun email provider.
DNSTarkistaer still shows the old nameservers
This usually means DNS resolvers are still using cached inftaimation.
Jos the NiceNIC nameserver settings are ctairect, wait ftai propagation rather than changing them again.
Your verkkotunnus remains rekisteröied at NiceNIC throughout the process. Cloudflare simply becomes the authtaiitative DNS provider.
Ftai verkkotunnus registration ja management, visit NiceNIC Verkkotunnus Services.
