You connected your domain, but typing it in a browser still shows your old site, an error, or nothing. Your site itself is fine: it keeps working on its apps.veldhost.eu address the whole time. What is missing is the last step, where the domain points at us.
Why it happens
Your domain goes live on veldhost only once public DNS sends it to us. We check that on our own, and the moment it is true we issue the certificate and put the domain live. Until then, visitors keep reaching wherever the domain pointed before.
So the cause is nearly always one of these:
- The nameserver change was never made, did not save at the registrar, or only one of the two nameservers was replaced.
- You kept your DNS elsewhere, but
@andwwwdo not point at our address yet. - The domain was live, then its nameservers were moved away from us.
- DNSSEC at the registry does not match the DNS that now answers, so validating resolvers refuse the domain.
Fix it
1. Read the Domains tab
Open Sites → your site → Domains. The DNS column tells you where you are (on a phone it is hidden; use a wider screen):
| It says | What it means |
|---|---|
| waiting for DNS | We have not yet seen the domain point at us. Go to step 2. |
| going live | It points at us; we are issuing the certificate. This takes a few minutes. |
| on our nameservers or points at us by address | Live. If the browser still shows the old site, go to step 4. |
| not pointing at us or not reaching us | It was live, but no longer points at us. Go to step 3. |
| certificate failed | The domain points at us, but the certificate could not be issued. See HTTPS certificate still pending. |
2. "waiting for DNS": check the change at your registrar
The notice under the table, Waiting for YOUR_DOMAIN to point at us, names the two nameservers to set and says when we last checked.
- Sign in where the domain is registered and look at its nameservers. Both entries must be the two shown in the portal, and nothing else. A mix of old and new nameservers fails some of the time, which is harder to spot than failing outright.
- Prefer to keep your DNS where it is (Cloudflare, for example)? Then point
@andwwwat the address in the notice instead. If the notice shows What we see ›, it opens the domain's Point it at us by address section, which compares each record with what public DNS answers now and shows Verified once our check gets through. - Wait. We keep checking every few minutes at first, then less often, for as long as the domain stays connected. You do not need to press anything.
If the notice says This has been waiting since …, the change most likely did not save at the registrar. Check there again.
Registered the domain with us? Open Domains → your domain. The Nameservers table puts the Registry, Public resolvers and Expected nameservers side by side. Split delegation means only some of them are ours. To change them, see Change a domain's nameservers.
3. "not pointing at us": point it back
The tab says YOUR_DOMAIN no longer points at our nameservers, so its certificate will not renew, or, for a domain pointed by address, that it no longer reaches our server. Someone changed the nameservers or the @/www records since the domain went live. Put them back as in step 2. If the move was on purpose, the site now lives wherever the domain points.
4. Live in the portal, old site in your browser
Resolvers and browsers keep old answers for a while: most changes show within an hour, some take longer. Generic advice, not specific to veldhost: try a private window, or another network such as your phone's mobile data.
5. The domain does not resolve at all
If the domain stopped working right after you moved its nameservers and DNSSEC was on, see Domain dark after DNSSEC or a nameserver change.
Still stuck?
Your AI assistant can check for you: get_domain_registrar compares the nameservers on file at the registry with what public resolvers answer, and reports the DNSSEC state. If that does not explain it, contact us with the domain name and we will look with you.