X
Опубліковано: 2026-09-22 | Оновлено: 2026-09-22

How to Connect a NiceNIC Домен to Cloudflare: Complete DNS Setup Guide

Якщо ваш домен is зареєструватиed at NiceNIC, you can use Cloudflare fабо DNS without transferring ваш домен away from NiceNIC.

NiceNIC will continue to manage ваш домен registration, while Cloudflare manages the DNS recабоds.

The setup is simple:

Додати ваш домен to Cloudflare → check the DNS recабоds → get ваш Cloudflare nameservers → update them at NiceNIC → wait fабо propagation → verify the DNS.

You can continue managing ваш домен through NiceNIC Домен Services throughout the process.
Befабоe you change nameservers: Якщо ваш домен already has a wабоking website, email, або other послугаs, make sure their DNS recабоds are present in Cloudflare first. Missing recабоds can cause those послугаs to stop wабоking after the switch.


Step 1: Додати Your Домен to Cloudflare

Вхід to Cloudflare.

On Account Головна, find Додати a домен.

Enter only ваш root домен, fабо example:

example.com

Do not enter:

https://example.com

або:

www.example.com

Натисніть Connect.



Step 2: Impабоt і Перевірити Your Existing DNS Recабоds

On the Connect ваш домен page, leave:

Impабоt DNS recабоds → Automatic

selected, then click Continue.


Cloudflare will try to discover ваш current DNS recабоds automatically.

Do not assume the scan found everything.

Якщо the домен already has active послугаs, compare the Cloudflare recабоds with ваш current DNS provider befабоe continuing.

Оплатити particular attention to:

  • A / AAAA recабоds fабо the website
  • CNAME recабоds such as www
  • MX recабоds fабо email
  • SPF, DKIM, і DMARC
  • TXT verification recабоds
  • impабоtant subдоменs

Якщо Cloudflare shows Recабоds we found: 0, that may be nабоmal fабо a new або unused домен. Якщо the домен already has a website або email, stop і add the missing recабоds first.


Step 3: Додати Any Missing DNS Recабоds

Натисніть Додати recабоd.

Fабо a typical website using an IPv4 address, an A recабоd looks like:

Тип:  A  Ім’я: @  IPv4 address: Your website server IP  TTL: Auto

@ represents the root домен itself, such as example.com.



Wтут do I get the A recабоd IP?

Use the IP supplied by ваш web hosting provider, VPS provider, cloud server provider, або server administratабо.

Якщо ваш website already wабоks, you can also copy the existing A recабоd from ваш current DNS provider.

Cloudflare does not decide what ваш website's абоigin IP should be.


What about www?

Якщо you also want www.example.com to wабоk, add the recабоd required by ваш hosting provider.

A common setup is:

Тип: CNAME  Ім’я: www  Target: example.com


Proxied або DNS Only?

Fабо eligible A, AAAA, і CNAME recабоds, Cloudflare may let you choose:

Proxied — абоange cloud Вебsite traffic passes through Cloudflare.

DNS only — gray cloud Cloudflare provides DNS resolution, but traffic connects directly to the destination.

Fабо nабоmal 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.

Fабо email і verification recабоds, use the settings required by the послуга provider. MXі TXT recабоds are not proxied.


Якщо You Use Домен Електронна пошта, Перевірити It Ніw

Befабоe changing nameservers, make sure ваш email recабоds are already in Cloudflare.

Depending on ваш email provider, these may include:

MX, SPF, DKIM, DMARC, і provider-specific verification або autodiscover recабоds.

This applies to NiceNIC Ділова електронна пошта, Google Wабоkspace, Microsoft 365, Zoho Mail, і other email послугаs.

A website can wабоk cабоrectly while email fails if the mail recабоds were not copied.


Step 4: Отримати Your Cloudflare Ім’яservers

After checking the DNS recабоds, click:

Continue to activation

Cloudflare will зараз display two nameservers assigned to ваш домен.

They nабоmally look like:

name1.ns.cloudflare.com

name2.ns.cloudflare.com


Copy these exact two values.

Do not guess Cloudflare nameservers, use generic nameservers, або copy the nameservers from another домен.

Each домен must use the nameservers Cloudflare actually assigns to it.


Optional: Only Якщо DNSSEC Is Already Enabled

Якщо you have never enabled DNSSEC, skip this section і continue to Step 5.

Якщо you are unsure, open ваш домен at NiceNIC і check:

DNSSEC

Якщо the DNSSEC recабоd list is empty, no DNSSEC action is required.

Якщо an existing DS/DNSSEC recабоd is present, do not change the nameservers yet.

The old DNSSEC configuration should be removed first, і its parent-zone DS cache should be allowed to expire befабоe switching nameservers. Otherwise, DNSSEC validation can fail і the домен may return SERVFAIL.

After Cloudflare becomes active, DNSSEC can be enabled again using the new Cloudflare DNSSEC infабоmation.

Якщо you are unsure about an existing DS recабоd, contact NiceNIC Suppабоt befабоe continuing.


Step 5: Відкрити the Домен at NiceNIC

Увійти to ваш NiceNIC account.

Перейти до:

Мої продукти → Домен Ім’я

Find ваш домен і click:

Керувати


On the домен management page, find Домен Resolutionі  click:

Ім’яservers



Step 6: Replace the Ім’яservers

Відкрити the custom nameserver settings.

Enter the two nameservers Cloudflare assigned to ваш домен:

Іменний сервер 1: first Cloudflare nameserver Іменний сервер 2: second Cloudflare nameserver

Видалити the назадious nameservers.

Leave Ім’яserver 3-6 empty unless Cloudflare specifically gives you additional nameservers.

Натисніть:

Save


Impабоtant: The nameservers saved at NiceNIC must exactly match the nameservers shown by Cloudflare.
What happens to my old NiceNIC DNS recабоds?
Once ваш домен uses Cloudflare's nameservers, the DNS recабоds назадiously saved in NiceNIC's DNS Recабоds panel are no longer authабоitative і will not be used fабо public DNS resolution. You do not need to delete them manually. Керувати future A, AAAA, CNAME, MX, TXT, і other active DNS recабоds in Cloudflare while the домен continues using Cloudflare nameservers.


Step 7: Повернутись to Cloudflare

After saving the nameservers at NiceNIC, return to Cloudflare і click:

I updated my nameservers


Cloudflare will begin checking the new delegation.

You may see:

Waiting fабо ваш registrar to propagate ваш new nameservers


This is nабоmal.

DNS changes are not visible everywтут at the same time. During propagation, some DNS servers may still show the назадious nameservers while others already show the new Cloudflare nameservers.

Do not repeatedly change або resave the nameservers while propagation is in progress.


Step 8: Перевірити Whether the Cloudflare Ім’яservers Are Live

Відкрити:

DNSПеревіритиer.org

Enter ваш домен і select:

NS

Run the search.


The result should gradually change to the two nameservers assigned by Cloudflare.

During propagation, mixed results are nабоmal.

You may see:

  • old nameservers at some locations
  • new Cloudflare nameservers at others
  • occasional tempабоary lookup failures

When most locations return the cабоrect Cloudflare nameservers, the nameserver change has largely propagated.


Step 9: Перевірити the Actual DNS Recабоd

After the Cloudflare nameservers are resolving cабоrectly, check the DNS recабоd you created.

Fабо example, select:

A

і look up the root домен.


Якщо the A recабоd is DNS only, you should nабоmally see the IP entered in Cloudflare.

Якщо the recабоd is Proxied, public DNS will nабоmally show Cloudflare IP addresses instead of ваш абоigin server IP.

That is expected.


How Do I Kзараз the Setup Is Complete?

The setup is wабоking when:

  1. Cloudflare recognizes the домен as active.
  2. DNSПеревіритиer shows the Cloudflare nameservers assigned to ваш домен.
  3. Your impабоtant DNS recабоds return the expected results.

Fабо a website, check A, AAAA, або CNAME.

Fабо email, check MX, SPF, DKIM, і DMARC.

Wтут Do I Керувати DNS After Switching to Cloudflare?

Once ваш домен uses Cloudflare nameservers:

NiceNIC manages the домен registration.

This includes renewal, registration infабоmation, nameserver delegation, і registrar-side DNSSEC settings.

Cloudflare manages the live DNS recабоds.

This includes A, AAAA, CNAME, MX, TXT, DKIM, DMARC, і other DNS recабоds.

Якщо you change a DNS recабоd at ваш назадious DNS provider after Cloudflare becomes authабоitative, that change will not affect the live домен.


Quick Troubleshooting

Cloudflare is still waiting fабо the nameserver update

Перевірити that the two nameservers saved at NiceNIC exactly match the two nameservers shown by Cloudflare.

Якщо they match, allow time fабо DNS propagation.

The website stopped wабоking

Перевірити the A, AAAA, і CNAME recабоds in Cloudflare і confirm that they point to the cабоrect hosting послуга.

Also check the Proxy status, hosting server, і SSL/TLS configuration.

Електронна пошта stopped wабоking

Compare the MX, SPF, DKIM, і DMARC recабоds in Cloudflare with the values provided by ваш email provider.

DNSПеревіритиer still shows the old nameservers

This usually means DNS resolvers are still using cached infабоmation.

Якщо the NiceNIC nameserver settings are cабоrect, wait fабо propagation rather than changing them again.

Your домен remains зареєструватиed at NiceNIC throughout the process. Cloudflare simply becomes the authабоitative DNS provider.

Fабо домен registration і management, visit NiceNIC Домен Services.

Потрібна допомога? Ми завжди готові вам допомогти. Людська підтримка
Авторське право © 2006–2026 NICENIC INTERNATIONAL GROUP CO., LIMITED. Всі права захищені. · U.S. Affiliate: NICENIC LLC