I changed the nameserver in Cafe24 but the site still won't load. How long do I wait?

A nameserver delegation change is the slow one: Cafe24's own guidance says it can take roughly 24–48 hours for the registry to publish the new NS records and for resolvers to pick them up. That's genuinely different from an A-record edit, which is usually visible in minutes once your nameservers are correct. So the real question isn't 'how long' — it's *which layer* you changed. If you switched nameservers, expect up to two days and confirm the registry actually shows the new NS. If you only edited an A record and it's been more than an hour, the NS change isn't your problem; something else is, and waiting won't fix it.

Why can't I edit A records in the Cafe24 panel for my own domain?

Because Cafe24's DNS management only controls a domain that is actually delegated to Cafe24's nameservers. If your domain still points its NS records at another provider — a registrar you bought it from, or a previous host — then Cafe24's DNS panel is editing a zone nobody is asking. The authoritative answers are coming from the other provider's nameservers, so your A/CNAME edits in Cafe24 have no effect. Either move the nameservers to Cafe24 (and wait out the 24–48h delegation), or edit the records where the domain is actually delegated.

It worked for me but a colleague still gets the old page. Did the change fail?

Almost certainly not — this is negative caching and stale TTLs, not a broken change. When a name failed to resolve or resolved to an old IP, resolvers cache that answer for the record's TTL; a colleague on a different network (or a phone on mobile data) may still be inside that cached window while your resolver has already refreshed. The fix is patience plus verification: check the record from multiple resolvers to confirm the *authoritative* answer is now correct, then let the old TTL expire. If different resolvers disagree, you're mid-propagation, not broken.

Views: 23

Cafe24 Domain Not Connecting? Fix DNS & Nameservers

Cafe24 domain not connecting after a nameserver change? Check registrar NS, A/CNAME records, and propagation in 4 steps to find the broken layer. Free instant check.

Check your domain for this issue now

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

Problem

You bought a domain on Cafe24 (or pointed one there), set it up, and the site won’t load — a timeout, a “server not found,” or the old page instead of the new one. The frustrating part is that the domain clearly exists; you own it, you can see it in your Cafe24 account. What’s broken is one specific layer in the chain between owning a name and having it answer with the right address.

Symptoms

The domain resolves to nothing (NXDOMAIN / “server not found”) or times out in the browser.
It loads an old site, a parking page, or Cafe24’s default page instead of your content.
You changed the nameserver and nothing happened — hours later it still won’t connect.
The Cafe24 DNS panel won’t let you edit A/CNAME records, or your edits there have no visible effect.
It works on one device or network but not another, or for you but not a colleague.

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 Cafe24 “not connecting” problem is almost always a mismatch between them. Get the order straight and the fix is obvious.

Layer 1 — the registrar (who owns the name). This is the account that holds the domain registration. Its one job that matters here is pointing the domain’s nameserver (NS) records at whoever will answer DNS queries. If you bought the domain elsewhere and want Cafe24 to host DNS, this is where you change the NS to Cafe24’s — and that change takes roughly 24–48 hours to propagate through the registry.

Layer 2 — the nameserver (who answers). Whatever NS the registrar points to is the authority for your domain. This matters because Cafe24’s DNS editor only controls a domain delegated to Cafe24’s nameservers. If your NS still points at another provider, editing A records in the Cafe24 panel changes a zone nobody queries. The authoritative answer keeps coming from the old nameserver.

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 A record is usually live in minutes, not days.

The single most common Cafe24 mistake is confusing Layer 1 and Layer 2 — editing records in Cafe24 while the domain is still delegated somewhere else, then waiting for a change that will never appear because it’s being made in the wrong place.

Top 3 Causes

Nameservers not actually pointed at where you’re editing DNS. You’re editing A/CNAME records in Cafe24, but the domain’s NS records at the registrar still point at another provider (or vice versa). The tell: your edits have no effect and the authoritative nameserver for the domain isn’t the one you think it is.
A nameserver change that simply hasn’t propagated yet. You correctly moved the NS to (or from) Cafe24, but you’re inside the 24–48h delegation window. The tell: the registry still shows the old NS, or resolvers disagree about which nameserver is authoritative.
A missing or wrong A/CNAME record, or negative caching after a fix. The nameserver is right but the record points at the wrong IP, is absent, 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.

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 multiple 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 done and the record itself is the problem.

Resolution Checklist

Run DNS Lookup and read the NS records first — confirm the domain is delegated to the nameserver you intend to manage (Cafe24’s, or your other provider’s).
If the NS is wrong, change it at the registrar (where the domain is registered), then expect 24–48 hours before it takes effect.
Only edit A/CNAME records in the panel of whoever is actually authoritative — editing DNS in Cafe24 while delegated elsewhere does nothing.
Confirm the A record points at the correct server IP (or the CNAME at the correct target), with no leftover parking/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, the DNS layer is done — check whether the server is actually serving on the target 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 moved off DNS entirely — it’s the web server or hosting on that IP, not the domain connection.
If the domain resolves fine but is unreachable only from Korea, rule out an administrative block (in Korea, the Korea Communications Standards Commission can order access blocking) before assuming a DNS fault — that’s a separate process handled through the registrar/host, not a records change.