When you onboard a domain to Cloudflare, you don't pick a generic set of nameservers from a static global list. Instead, Cloudflare assigns your specific zone a pair of unique hostnames—often named after historical figures or cities—tied to its anycast network. Understanding how these assignments work, where to find your allocated server records, and how to configure them at your registrar prevents common migration downtime.
Every Cloudflare zone relies on redundant name resolution to keep web traffic flowing. Whether you're moving a high-traffic e-commerce store or setting up a personal blog, getting the configuration right ensures your site resolves globally in milliseconds. Let's look at how these nameservers operate, how to update them, and what to do if propagation stalls.
Locating Your Assigned Cloudflare Nameservers
When you add a new domain to your account, the platform inspects your existing DNS records and generates two distinct nameserver hostnames. You can't manually choose these names; they're locked to your specific zone assignment.
To find your designated hostnames, follow these steps:
- Log in to your Cloudflare Dashboard and select your target domain.
- Navigate to the Overview page for that zone.
- Scroll down to the right-hand sidebar where the Cloudflare Nameservers section displays your two assigned addresses (for example,
nsak.ns.cloudflare.comandolga.ns.cloudflare.com). - Copy both hostnames exactly as shown. Avoid adding trailing dots or extra spaces when pasting them into your registrar.
If you manage your infrastructure programmatically, you can query the API using an endpoint with appropriate token permissions to retrieve the active zone details without opening the web interface.
Public Resolvers Versus Authoritative Nameservers
It's common to confuse Cloudflare's authoritative nameservers with its public recursive resolvers. They serve completely different functions in internet architecture.
Public resolvers handle outgoing lookups from consumer devices. If you configure your local network or router to use Cloudflare's public IPs, you're using 1.1.1.1 and 1.0.0.1 (or their IPv6 equivalents 2606:4700:4700::1111 and 2606:4700:4700::1001). These IPs resolve external web addresses for your browser.
Authoritative nameservers, by contrast, store the official DNS records for domains hosted on the network. When someone types your web address into a browser, the global DNS hierarchy points them to your specific Cloudflare-assigned hostnames to find your server's IP address. Mixing up these two systems is a frequent source of configuration errors during initial site setups.
Step-by-Step Registrar Update Process
Once you have your assigned hostnames, you must update them at your domain registrar—the company where you originally purchased your domain name, such as Namecheap, GoDaddy, or Porkbun.
Before making changes, check if DNSSEC is active on your domain. If it is, disable it temporarily at your registrar. Leaving DNSSEC enabled while swapping nameservers often triggers validation failures, rendering your site completely unreachable.
- Log in to your domain registrar account panel and locate your domain management or DNS settings page.
- Look for the Nameservers section, which usually defaults to your registrar's internal values.
- Switch the setting from default/parked nameservers to Custom Nameservers.
- Enter your two assigned Cloudflare hostnames into the designated primary and secondary fields.
- Save your changes and confirm that no residual third-party entries remain in those fields.
After updating, global propagation can take anywhere from a few minutes to a couple of hours depending on your registrar's registry update speed and existing local caching across internet service providers.
Handling Custom Nameservers and Enterprise Setups
For businesses running enterprise environments or strict white-label setups, standard alphanumeric nameserver assignments might not meet branding requirements. Enterprise plans allow the use of Custom Nameservers (sometimes referred to as vanity nameservers), letting you use your own domain for the nameserver hostnames, such as ns1.yourdomain.com.
When configuring custom nameservers, you must define appropriate glue records at your registrar. Glue records provide the direct IPv4 and IPv6 addresses associated with your custom nameserver hostnames, preventing circular dependency loops during recursive lookups. Cloudflare provides specific IP assignments for these custom setups, which must match the entries configured in your account's DNS settings panel.
Common Migration Pitfalls to Avoid
Moving a live production website to a new DNS provider requires precision. Overlooking minor configuration details can cause unexpected downtime or broken mail delivery.
- Forgetting MX and TXT Records: When Cloudflare auto-scans your old DNS zone, it usually captures standard web and mail records. Always double-check that critical email routing entries and domain verification tokens migrated accurately before flipping the switch.
- Premature SSL/TLS Adjustments: Keep your SSL mode set to Flexible or Full appropriately based on your origin server configuration before propagation completes to prevent browser privacy warnings.
- Ignoring TTL Settings: Lowering your Time-To-Live values a day prior to a migration helps old cache entries expire faster, speeding up the transition to the new infrastructure.
Frequently Asked Questions
Can I choose which nameserver names are assigned to my domain?
No, Cloudflare automatically assigns nameserver hostnames when you add a zone. You cannot manually request a specific pair unless you are on an enterprise plan that supports custom nameserver sets.
Why does my dashboard show different nameservers than my colleague's domain?
Cloudflare distributes zones across a massive pool of infrastructure hostnames to balance global query loads. Different accounts or even different domains within the same account frequently receive unique pairs.
What happens if I only enter one nameserver at my registrar?
Most domain registries and internet standards require at least two functional nameservers for redundancy. Entering only one can cause intermittent resolution failures if that specific node encounters temporary routing congestion.
How do I verify that my new nameservers are active?
You can use command-line utilities like dig or online lookup tools to query your domain's apex records. If the authoritative servers returned match the hostnames displayed in your Cloudflare dashboard, the migration is complete.