How to Change Nameservers on GoDaddy (and Wire a Domain)

Rocco changed the nameservers, then stared at the propagation timer like it owed him money.

To change nameservers on GoDaddy, sign in, open My Products → Domains (the Domain Portfolio), select your domain, find the Nameservers section, click Change, choose I'll use my own nameservers (or Enter my own nameservers), enter the two or more nameservers from your DNS host, and save. Propagation takes anywhere from a few minutes to 48 hours. Below is the full flow, how to point the domain at Cloudflare or Vercel, and how Ringtail wires the domain from accounts you connected once — using official APIs, never a browser bot.

Where do you change nameservers on GoDaddy?

You change them in the Domain Portfolio (formerly "My Domains"), reached from godaddy.com via the account menu → My Products → Domains. Click the domain you want to edit, and scroll to the Nameservers panel on the domain's settings page. That's where GoDaddy shows whether the domain is on its default nameservers or custom ones.

Changing nameservers is different from editing DNS records. Nameservers decide which service answers DNS queries for your domain; records (A, CNAME, TXT) are the answers themselves. When you move nameservers to Cloudflare or Vercel, that host takes over records — so manage them there afterward, not in GoDaddy.

What are the steps to change GoDaddy nameservers?

Six steps:

1. Sign in and open My Products → Domains (the Domain Portfolio).
2. Select the domain you want to change.
3. Scroll to the Nameservers section and click Change (or Edit Nameservers).
4. Choose I'll use my own nameservers — GoDaddy may label this Enter my own nameservers.
5. Enter each nameserver from your DNS host. Cloudflare and Vercel give you two; some hosts give more. Remove GoDaddy's defaults.
6. Click Save. GoDaddy shows a confirmation and, often, a warning that the change can take up to 48 hours to propagate.

That's it — no key to copy here, because nameservers are public configuration, not a secret.

What nameservers do you enter for Cloudflare or Vercel?

You enter the exact nameservers your DNS host assigns you — they're specific to your account, not generic.

• Cloudflare: after you add the site in the Cloudflare dashboard, it assigns you two nameservers like dana.ns.cloudflare.com and rob.ns.cloudflare.com. Copy those exact two into GoDaddy. Then manage DNS records in Cloudflare — where a scoped Cloudflare API token lets tooling edit records for you.
• Vercel: if you use Vercel's nameservers, add the domain under your project's Domains settings and Vercel shows you ns1.vercel-dns.com and ns2.vercel-dns.com (or similar). Alternatively, keep GoDaddy's nameservers and just add the A/CNAME records Vercel gives you — that avoids the nameserver change entirely for a single subdomain.

Copy the assigned values exactly; a typo in a nameserver silently breaks resolution.

How long does GoDaddy nameserver propagation take?

It ranges from a few minutes to 48 hours, because DNS resolvers around the world cache the old nameservers until their TTL expires. Most changes resolve within an hour or two, but don't panic if a stale resolver still points at the old host — that's normal caching, not a failure.

Check progress from your terminal instead of guessing:

dig NS acme.com +short

When the output lists your new nameservers (your Cloudflare or Vercel pair), the change has propagated for you. Run it again from a different network to sanity-check.

How does Ringtail wire the domain for you?

Once you've connected your DNS host to Ringtail one time, Ringtail wires the domain for you by driving that host's official API — adding the A, CNAME, and TXT records your app and email need, from the same .env.example-driven flow that mints your keys. If your DNS lives at Cloudflare, Ringtail uses the Cloudflare API to set the records; you approve the connection once, and provisioning a new project's DNS becomes zero-touch.

Ringtail is honest about the boundary. It uses official provider APIs only — never a browser bot with your GoDaddy login. Where a registrar exposes an API for the action, Ringtail drives it; where a step genuinely requires the registrar's console — like the nameserver switch itself on some plans — Ringtail hands you a guided flow and you click the button, rather than a bot puppeting your credentials. That honesty is the point. Install it once:

curl -fsSL ringtail.sh | sh
ringtail up

For the wider pattern of provisioning a whole project's keys and DNS from one manifest, see how to stop juggling 15 API keys on every new project and least-privilege API key provisioning.

FAQ

Where do I change nameservers in GoDaddy?

Sign in to GoDaddy, open My Products → Domains (the Domain Portfolio), select your domain, and scroll to the Nameservers section on its settings page. Click Change, choose I'll use my own nameservers, enter the nameservers from your DNS host, and save. This is separate from editing DNS records, which you do at your new host after the switch.

How long do GoDaddy nameserver changes take to propagate?

Nameserver changes can take from a few minutes up to 48 hours, because DNS resolvers cache the previous nameservers until their TTL expires. Most changes resolve within an hour or two. Verify with dig NS yourdomain.com +short — when it lists your new nameservers, the change has propagated for you.

What nameservers do I use to point GoDaddy at Cloudflare?

Use the two nameservers Cloudflare assigns your specific account — for example dana.ns.cloudflare.com and rob.ns.cloudflare.com — shown in the Cloudflare dashboard after you add the site. They're unique to your account, so copy the exact pair Cloudflare gives you and remove GoDaddy's defaults.

Can Ringtail set up my domain's DNS records for me?

Yes, for the records themselves. After you connect your DNS host (such as Cloudflare) to Ringtail once, Ringtail uses the host's official API to add the A, CNAME, and TXT records your project needs — value-free and driven from your .env.example. It never uses a browser bot with your registrar login; where a step requires the registrar console, it hands you a guided flow instead.