<![CDATA[AdminsForum - Cloudflare]]> https://adminsforum.com/ Thu, 15 Oct 2026 05:17:48 +0000 MyBB <![CDATA[Add a Domain to Cloudflare Free: DNS and Nameservers]]> https://adminsforum.com/Thread-guide-add-a-domain-to-cloudflare-free-dns-and-nameservers Sun, 11 Oct 2026 01:54:11 +0800 DEV]]> https://adminsforum.com/Thread-guide-add-a-domain-to-cloudflare-free-dns-and-nameservers Quick answer
To add a domain to Cloudflare Free, connect the registered domain, choose the Free plan, review or add its DNS records, and replace the domain's nameservers at your registrar with the two assigned by Cloudflare. Wait for Cloudflare to confirm activation before treating the migration as complete.

Before you start
  • A registered domain and access to its registrar account.
  • A Cloudflare account.
  • Your website server's public IP address.
  • For an existing website, a copy of all current DNS records, including email records.
This guide uses our new lab domain, adminslab.com. Adding it to Cloudflare does not transfer its registration. These DNS steps apply to any hosting panel, not only aaPanel.

1. Connect your domain
In the Cloudflare dashboard, open Domains and choose Add domain, then Connect a domain. Enter the registered root domain, such as adminslab.com, without https://, a path, or www. Continue and select the Free plan.

2. Review the DNS scan
Cloudflare can scan for existing DNS records. Compare its results with your current DNS provider before changing nameservers. Keep required A, AAAA, CNAME, MX and TXT records, including SPF, DKIM and DMARC if you use email. A scan is not a complete backup.
Our new lab domain had no records to import, so we added the records manually.

3. Add website DNS records
Open DNS > Records > Add record. For the root domain, choose Type A, enter @ as the Name and your server's IPv4 address as the Content. Save it. Repeat for www if your website will use that hostname.

Our lab records are:
Code:
Type Name IPv4 address Proxy status TTL A @ 217.217.235.82 DNS only Auto A www 217.217.235.82 DNS only Auto A aapanel 217.217.235.82 DNS only Auto
Use your own server's address, not the example IP. The aapanel record is an optional lab subdomain; adding DNS does not create a website or bind the panel to that hostname.

We chose DNS only while preparing the lab website and its origin certificate. DNS-only traffic goes directly to the server and does not receive Cloudflare's proxy caching or web security features. We will cover proxying and HTTPS separately after the website works.

4. Update nameservers at your registrar
Cloudflare assigns two nameservers to your domain. Open the nameserver settings at the company where you registered the domain, replace the existing nameservers with your assigned pair, and save.

[Image: attachment.php?aid=13]

The highlighted nameservers belong to this lab domain. Use the pair shown in your own Cloudflare dashboard. Change nameservers in the registrar's nameserver settings, rather than adding them as ordinary DNS records.
If the domain already uses DNSSEC, follow Cloudflare's migration instructions for the existing DNSSEC/DS configuration before switching, then configure DNSSEC again after activation.

5. Confirm activation
After saving the nameservers at the registrar, return to Cloudflare and request a nameserver check if offered. Allow time for the delegation change to be detected. The domain should show Active when Cloudflare confirms the change.
Update, 10 October 2026: Cloudflare has confirmed activation for our lab domain. The DNS-only website records resolve to 217.217.235.82. Proxying is still intentionally off while we configure the website and origin HTTPS.

Common questions
Do I need to buy the domain again?
No. Connect the domain you already own. Its registration stays with your existing registrar.

Why does Cloudflare show a proxy warning?
Our lab records are DNS only. This is intentional for initial setup; it does not mean Cloudflare's proxy protections are enabled.

Does a DNS record make the website ready?
No. Create the website on the server, add the matching domain, and configure HTTPS. DNS only tells visitors where to connect.

What if activation stays pending?
Check that the registrar has the exact assigned pair, that old nameservers were replaced, and that an old DNSSEC DS record is not interfering. Do not repeatedly change unrelated DNS settings.

Official reference
Cloudflare full DNS setup instructions

Tested: Cloudflare Free dashboard, 10 October 2026. Original lab walkthrough and AdminsForum screenshot. Website hosting and SSL will be covered separately.

.jpg   cloudflare-annotated-20261010.jpg (Size: 107.98 KB / Downloads: 19) ]]> Quick answer
To add a domain to Cloudflare Free, connect the registered domain, choose the Free plan, review or add its DNS records, and replace the domain's nameservers at your registrar with the two assigned by Cloudflare. Wait for Cloudflare to confirm activation before treating the migration as complete.

Before you start
  • A registered domain and access to its registrar account.
  • A Cloudflare account.
  • Your website server's public IP address.
  • For an existing website, a copy of all current DNS records, including email records.
This guide uses our new lab domain, adminslab.com. Adding it to Cloudflare does not transfer its registration. These DNS steps apply to any hosting panel, not only aaPanel.

1. Connect your domain
In the Cloudflare dashboard, open Domains and choose Add domain, then Connect a domain. Enter the registered root domain, such as adminslab.com, without https://, a path, or www. Continue and select the Free plan.

2. Review the DNS scan
Cloudflare can scan for existing DNS records. Compare its results with your current DNS provider before changing nameservers. Keep required A, AAAA, CNAME, MX and TXT records, including SPF, DKIM and DMARC if you use email. A scan is not a complete backup.
Our new lab domain had no records to import, so we added the records manually.

3. Add website DNS records
Open DNS > Records > Add record. For the root domain, choose Type A, enter @ as the Name and your server's IPv4 address as the Content. Save it. Repeat for www if your website will use that hostname.

Our lab records are:
Code:
Type Name IPv4 address Proxy status TTL A @ 217.217.235.82 DNS only Auto A www 217.217.235.82 DNS only Auto A aapanel 217.217.235.82 DNS only Auto
Use your own server's address, not the example IP. The aapanel record is an optional lab subdomain; adding DNS does not create a website or bind the panel to that hostname.

We chose DNS only while preparing the lab website and its origin certificate. DNS-only traffic goes directly to the server and does not receive Cloudflare's proxy caching or web security features. We will cover proxying and HTTPS separately after the website works.

4. Update nameservers at your registrar
Cloudflare assigns two nameservers to your domain. Open the nameserver settings at the company where you registered the domain, replace the existing nameservers with your assigned pair, and save.

[Image: attachment.php?aid=13]

The highlighted nameservers belong to this lab domain. Use the pair shown in your own Cloudflare dashboard. Change nameservers in the registrar's nameserver settings, rather than adding them as ordinary DNS records.
If the domain already uses DNSSEC, follow Cloudflare's migration instructions for the existing DNSSEC/DS configuration before switching, then configure DNSSEC again after activation.

5. Confirm activation
After saving the nameservers at the registrar, return to Cloudflare and request a nameserver check if offered. Allow time for the delegation change to be detected. The domain should show Active when Cloudflare confirms the change.
Update, 10 October 2026: Cloudflare has confirmed activation for our lab domain. The DNS-only website records resolve to 217.217.235.82. Proxying is still intentionally off while we configure the website and origin HTTPS.

Common questions
Do I need to buy the domain again?
No. Connect the domain you already own. Its registration stays with your existing registrar.

Why does Cloudflare show a proxy warning?
Our lab records are DNS only. This is intentional for initial setup; it does not mean Cloudflare's proxy protections are enabled.

Does a DNS record make the website ready?
No. Create the website on the server, add the matching domain, and configure HTTPS. DNS only tells visitors where to connect.

What if activation stays pending?
Check that the registrar has the exact assigned pair, that old nameservers were replaced, and that an old DNSSEC DS record is not interfering. Do not repeatedly change unrelated DNS settings.

Official reference
Cloudflare full DNS setup instructions

Tested: Cloudflare Free dashboard, 10 October 2026. Original lab walkthrough and AdminsForum screenshot. Website hosting and SSL will be covered separately.

.jpg   cloudflare-annotated-20261010.jpg (Size: 107.98 KB / Downloads: 19) ]]>