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

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.