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 Website 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

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.