Cloudflare Nameservers for a Name.com Domain

1. Quick answer: where Cloudflare nameservers come from

Cloudflare assigns two authoritative nameservers after the domain is added to a Cloudflare zone. Those two values are unique to the zone setup and should be copied from Cloudflare's onboarding or zone Overview screen.

At Name.com, the job is not to create DNS records. The job is to replace the registrar's current nameservers with the two Cloudflare nameservers, save the change, and then wait for Cloudflare to detect that the delegation has propagated.

• Get the two nameservers from Cloudflare, not from a blog post.
• Delete the old Name.com nameservers before saving.
• Add one Cloudflare nameserver per field.
• Keep at least two nameservers on the domain.
• Wait for propagation before diagnosing Cloudflare Pages or Search Console issues.

2. Why this step matters

Name.com is the registrar in this workflow. Cloudflare becomes the authoritative DNS provider after the nameservers are changed. That distinction is important: the domain is still registered at Name.com, but DNS records are controlled in Cloudflare.

Cloudflare's DNS documentation says nameservers need to point to the nameservers assigned in the Cloudflare account for Cloudflare DNS to become authoritative. In practical terms, this is what lets the Cloudflare dashboard manage records, proxy status, custom-domain activation, SSL, redirects, and later Search Console verification more cleanly.

This step is not a ranking trick. It is infrastructure cleanup. A clean DNS setup reduces the chance that the site has duplicate hosts, broken SSL, stale registrar parking records, or a sitemap on the wrong domain.

• Registrar: Name.com keeps domain registration and renewal.
• DNS provider: Cloudflare answers DNS after nameservers are changed.
• Hosting: Cloudflare Pages serves the static site after the custom domain is attached.

3. Start in Cloudflare, not Name.com

Do not guess the nameserver values. Add the domain to Cloudflare first and let Cloudflare assign the two nameservers for that zone. Cloudflare's full setup flow starts by adding the domain, reviewing DNS records, then changing nameservers at the registrar.

In our setup, Cloudflare showed a clear instruction screen with two assigned nameservers and a list of the old Name.com nameservers to remove. That screen is the source of truth for the values to enter at Name.com.

• Add the domain to Cloudflare.
• Review imported A, CNAME, and other DNS records before activation.
• Copy the assigned Cloudflare nameservers exactly.
• Keep the Cloudflare tab open while editing Name.com.

4. Replace nameservers inside Name.com

Name.com's support article for changing nameservers says to open My Domains, choose the domain, use Manage Nameservers, clear the current nameservers, add the new nameservers, and save the changes. The exact interface can change, but the concept is stable: remove the registrar defaults and add only the Cloudflare nameservers assigned to the zone.

In the solobuilderstack.com setup, the Name.com Manage Nameservers screen showed two Cloudflare nameservers added and a Save Changes panel. That final save matters. Leaving the page without saving means Cloudflare will continue waiting.

• Open Name.com > My Domains.
• Select the domain.
• Open Manage Nameservers.
• Delete the existing Name.com nameservers.
• Add the two Cloudflare nameservers.
• Click Save Changes.

5. Handle DNSSEC carefully

Cloudflare's nameserver setup documentation includes a DNSSEC check before updating the registrar. If DNSSEC is enabled at the old provider with old DS records, changing nameservers can cause resolution problems until the DNSSEC configuration matches the new provider.

Name.com has a DNSSEC management page under the domain's nameserver area, and its DNSSEC FAQ says Name.com can work with third-party DNS providers that support DNSSEC. For a beginner site, the safer first move is to keep DNSSEC off during the handoff, confirm the domain is active in Cloudflare, and only revisit DNSSEC after the site, custom domain, SSL, sitemap, and redirects are stable.

• If DNSSEC is on, understand it before changing nameservers.
• Do not copy random DS records from old setup notes.
• Re-enable DNSSEC later only with Cloudflare's current DNSSEC values and registrar-side setup.

6. Wait for Cloudflare activation before doing the next step

After saving nameservers at Name.com, Cloudflare may show a waiting state while it checks whether the registrar has propagated the new nameserver delegation. In this project, we clicked the Cloudflare check after saving and then waited until Cloudflare recognized the update.

This waiting period is normal. Repeatedly changing DNS records, adding duplicate zones, or submitting Search Console too early can create more confusion than progress. The practical milestone is simple: Cloudflare should show the domain as active before the Pages custom-domain work is treated as complete.

• Use Cloudflare's Check nameservers action after saving at Name.com.
• Wait for Cloudflare to show the domain is active.
• Then attach the apex and www hostnames to the Cloudflare Pages project.
• Only submit the sitemap after the final HTTPS domain and redirects work.

7. What this changes for Search Console and monetization

Changing nameservers is not a traffic source. It supports the foundation that later makes Search Console and monetization easier to manage. Once Cloudflare is authoritative, the same platform can manage DNS records, redirects, SSL, custom domains, sitemap availability, and Cloudflare-assisted Search Console verification.

For a new site, this is useful because early Search Console data is already sparse. The last thing the site needs is split signals between Name.com parking records, pages.dev, www, and apex hosts. A single DNS control plane helps keep the canonical site clean.

AdSense, affiliate links, and sponsorships should still wait. A working domain is only the infrastructure layer. The revenue layer depends on original useful pages, policy-safe navigation, Search Console demand, and trust.

• DNS handoff helps infrastructure quality.
• It does not create indexing, ranking, traffic, AI citations, or ad approval by itself.
• Use it as a prerequisite for clean publishing, not as a monetization shortcut.

8. What the current Search Console data suggests

The 2026-07-31 Search Console export showed this page with 309 impressions and 0 clicks. That is the clearest mismatch on the site: Google is testing the page for Cloudflare nameserver queries, but searchers are not clicking yet.

The fix is not to add ads or affiliate links. The fix is to make the page answer the query faster. A beginner searching cloudflare nameservers probably wants to know where the nameservers are, whether they should replace registrar nameservers, how long propagation takes, and what can break if DNSSEC or old nameservers are left in place.

• Keep the title focused on Cloudflare nameservers and Name.com.
• Answer the quick setup question in the first screen.
• Keep the DNSSEC warning visible.
• Link to sitemap and Search Console troubleshooting because those are the next problems after DNS handoff.