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

A nameserver change is the slow one. Dothome's own guidance is that after a nameserver change it can take roughly one to two days before the domain starts connecting, because the registry has to publish the new NS records and resolvers around the world have to pick them up. That's genuinely different from editing an A record, which is usually live in minutes once your nameservers are already correct. So the useful question isn't 'how long' — it's *which layer* you touched. 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 over an hour, the delegation isn't your problem; something else is, and more waiting won't fix it.

Why can't I edit A records in the Dothome DNS panel, or why do my edits do nothing?

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

It works for me but a colleague still sees the old page. Did the change fail?

Almost certainly not — this is stale caching, not a broken change. When a name resolved to an old IP or failed to resolve, 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 verification plus patience: 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: 12

Dothome Domain Not Connecting? Fix DNS & Nameservers

Dothome domain not connecting after a nameserver change? Check registrar NS, A/CNAME, 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 registered a domain on Dothome (or pointed one there for its free/low-cost hosting), set it up, and the site won’t load — a timeout, a “server not found,” or the old page instead of your new one. The maddening part is that the domain clearly exists: you own it, you can see it in your Dothome account, the panel shows it right there. 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 a default hosting page instead of your content.
You changed the nameserver and nothing happened — a day later it still won’t connect.
The Dothome DNS record panel won’t accept your A/CNAME edits, or 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 Dothome “not connecting” problem is almost always a mismatch between them. Get the order straight and the fix becomes 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 registered elsewhere and want Dothome to host DNS, this is where you set the NS to Dothome’s — and that change takes roughly one to two days to propagate. If you registered the domain at Dothome, the nameserver control lives in your Dothome domain-management panel instead.

Layer 2 — the nameserver (who answers). Whatever NS the registrar points to is the authority for your domain. This is the layer people trip over: Dothome’s DNS record editor only controls a domain delegated to Dothome’s nameservers. If your NS still points at another provider, editing A records in the Dothome panel changes a zone nobody queries. The authoritative answer keeps coming from the old nameserver, and your edits vanish into the void.

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. When you use Dothome’s nameservers, Dothome pre-creates its own NS records and an SOA for you; you add the A record — type A, the host, a TTL, the server IP — yourself. This is the fast layer: a corrected A record is usually live in minutes, not days.

The single most common Dothome mistake is confusing Layer 1 and Layer 2 — editing records in Dothome 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 Dothome, but the domain’s NS records 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) Dothome, but you’re inside the one-to-two-day delegation window. The tell: a lookup still shows the old NS, or resolvers disagree about which nameserver is authoritative.
A missing or wrong A/CNAME record, or stale 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 all 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 (Dothome’s, or your other provider’s).
If the NS is wrong, change it where the domain is registered (Dothome’s domain-management panel if you registered there, otherwise the other registrar), then expect one to two days before it takes effect.
Only edit A/CNAME records in the panel of whoever is actually authoritative — editing DNS in Dothome 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 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, the DNS layer is done — check whether the server is actually serving 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 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 (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.