I changed the nameservers in GoDaddy but the site still won't load. How long should I wait?

A nameserver change is the slow kind of DNS change. It has to be published by the registry for your TLD and then picked up by resolvers all over the world, which commonly takes up to 24–48 hours. That is genuinely different from editing an A record inside a zone you already control, which is usually live in minutes. So before you count hours, be sure which change you actually made. If you switched the domain's NS records — say from GoDaddy's default nameservers (the pair ending in .domaincontrol.com) to Cloudflare, or the other way around — expect up to two days, and confirm the authoritative NS has actually flipped before you assume anything is broken. If you only edited a record inside GoDaddy's DNS and it has been more than an hour, the delegation isn't your problem and more waiting won't fix it.

Why do my DNS record edits in GoDaddy have no effect?

Because GoDaddy's DNS editor only controls a domain that is actually delegated to GoDaddy's nameservers — the pair ending in .domaincontrol.com. A very common setup is: you registered the domain at GoDaddy but later delegated DNS elsewhere (Cloudflare, AWS Route 53, your host) by switching the NS to 'I'll use my own nameservers.' Once you do that, the external provider is authoritative, and anything you change in GoDaddy's DNS editor is changing a zone nobody queries. Read the domain's live NS records first: whoever they point at is the only place your edits take effect.

GoDaddy shows the new nameservers but a checker still shows the old ones. Did it fail?

Almost certainly not — you're mid-propagation. The value in your GoDaddy account is the intent; the value the world sees is whatever the registry has published and whatever resolvers have cached. Right after a change those two disagree for a while, especially if the old NS records had a long TTL. Query the domain's NS from several resolvers at once: if they all now show the new nameservers, you're done and just waiting out caches; if some still show the old set, the change is propagating and changing more settings now only adds new caches to wait on.

GoDaddy Nameserver Change Not Working? 4-Step Fix

Problem

You changed your domain’s nameservers in GoDaddy — or you’re trying to point the domain at a host, a website builder, or an external DNS provider — and it still won’t connect. A timeout, a “server not found,” or GoDaddy’s parking page instead of your content. The domain plainly exists; you can see it in your account. What’s broken is one specific layer between owning the name and having it answer with the right address, and with GoDaddy the usual trap is that GoDaddy can be your registrar and your DNS host — so it’s easy to change one when you meant the other.

Symptoms

The domain resolves to nothing (NXDOMAIN / “server not found”) or times out in the browser.
It loads GoDaddy’s parking page, an old site, or a host’s default page instead of yours.
You switched the nameservers and nothing happened — hours later it still won’t connect.
Record edits in GoDaddy’s DNS editor have no visible effect.
A nameserver lookup elsewhere still shows GoDaddy’s .domaincontrol.com set after you thought you’d moved DNS away (or vice versa).

The Three Layers That Have to Agree

A domain connecting is not one setting. It’s three layers stacked on top of each other, and a “not connecting” problem is almost always a mismatch between them. GoDaddy blurs the picture because it plays two roles — registrar and DNS host — so the first thing to get straight is which role you’re actually configuring.

Layer 1 — the registrar (who owns the name). This is the GoDaddy account that holds the registration. Its one job that matters here is pointing the domain’s nameserver (NS) records at whoever will answer DNS queries. By default GoDaddy points the domain at its own nameservers — a pair of hostnames ending in .domaincontrol.com, assigned to your account (don’t copy a specific pair from a blog post; use the ones GoDaddy shows for your domain). If you want an external provider to run DNS, this is the layer where you change the NS — and that change takes roughly 24–48 hours.

Layer 2 — the nameserver (who answers). Whatever the NS records point at is the authority for your domain. This is the layer people get wrong: a DNS editor only controls the domain if that editor’s nameservers are the ones in the NS records. If the NS still points at GoDaddy but you’re editing records at Cloudflare — or the reverse — the authoritative answers keep coming from the other side, and your edits do nothing.

Layer 3 — the DNS records (what the answer says). Once the right nameserver is authoritative, the A record (or CNAME) is the actual address the name resolves to. This is the fast layer: a corrected record inside the authoritative zone is usually live in minutes, not days.

In GoDaddy’s interface this maps to one screen. Open your Domain Portfolio, select the domain, and find the Nameservers section under DNS. You’ll see either GoDaddy’s default nameservers or a custom set. “I’ll use my own nameservers” (custom) is Layer 1 — delegating away. The separate DNS Records editor is Layer 3 — and it only matters if Layer 2 still points at GoDaddy. The single most common GoDaddy mistake is confusing Layer 1 and Layer 2: delegating DNS to an external provider and then still editing records in GoDaddy, or leaving the NS on GoDaddy while editing records somewhere else. Either way you wait for a change that will never appear, because it’s being made in a zone nobody is asking.

Top 3 Causes

Editing records in a zone that isn’t authoritative. You’re changing A/CNAME records in GoDaddy’s DNS editor, but the domain’s NS points at an external provider (or you moved DNS out and kept editing in GoDaddy). The tell: your edits have no effect, and the live NS records aren’t the ones you think they are.
A nameserver change that simply hasn’t propagated. You correctly switched the NS (to or from GoDaddy), but you’re inside the 24–48h delegation window. The tell: resolvers disagree about which nameserver is authoritative, or the old .domaincontrol.com set still shows.
A missing or wrong record, or caching after a fix. The nameserver is right but the A record is absent, points at the wrong IP, or you fixed it and a stale/negative cache is still serving the old answer. The tell: the authoritative nameserver returns the wrong record — or the right one, while some resolvers still serve the old value.

One note on values: use the exact record values your host or platform shows you in its own console — IPs and CNAME targets change, and a number copied from a three-year-old tutorial is how a correct-looking setup quietly fails. The layers below tell you where to put the record; the host tells you what it should be.

Diagnose with DechoNet

DNS Lookup shows the domain’s current NS records and its A/CNAME answers, so you can confirm which nameserver is authoritative and what it actually returns — the fastest way to catch a Layer 1/Layer 2 mismatch where you’re editing the wrong zone.
DNS Propagation Check queries resolvers around the world at once. If they disagree, you’re mid-propagation after a nameserver or record change; if they agree on a wrong answer, propagation is finished and the record itself is the problem.

Resolution Checklist

Run DNS Lookup and read the NS records first — confirm whether the domain is delegated to GoDaddy (the .domaincontrol.com set) or to an external provider.
Edit records only in the DNS editor of whoever the NS actually points at. If that’s GoDaddy, use GoDaddy’s DNS Records editor; if it’s an external provider, edit there.
If the NS itself is wrong, change it at GoDaddy (the registrar) under Nameservers, then expect 24–48 hours before it takes effect — don’t touch records in the meantime.
Confirm the A record points at the correct server IP (or the CNAME at the correct target) using the exact value your host shows, with no leftover parking or old-host record.
Use DNS Propagation Check across multiple resolvers; if they disagree, wait out the TTL rather than changing anything else.
If it resolves correctly but still won’t load, DNS is done — check whether the server is actually answering on that IP with an HTTP check.

When to Escalate

If DNS resolves to the correct IP everywhere but the site still won’t load, the problem has left DNS entirely — it’s the web server or hosting on that IP, not the domain connection.
If you moved the domain to an external DNS provider and it still won’t resolve after two days, re-check the NS values in GoDaddy character by character — a single typo in a custom nameserver hostname produces a lame delegation that quietly fails rather than erroring.

Check your own domain now

Free, no sign-up. Runs the exact check this guide describes and shows what to fix.