Add Website Hosts UK to your device
Install for quick access to hosting, tools, billing and support.
Learn why a domain may not be working, including DNS records, nameservers, propagation, expired domains, SSL and hosting issues.
Learn why a domain may not be working, including DNS records, nameservers, propagation, expired domains, SSL and hosting issues.
When a domain is not working, the issue is usually caused by one of five things: the domain has expired, the nameservers are wrong, DNS records are missing, DNS changes are still propagating, or the domain is pointing to the wrong hosting service.
This guide explains how to check the problem in the right order. Start with the domain status, then nameservers, DNS records, propagation, hosting IP address and SSL.
Avoid changing several DNS records at once. Domain problems are much easier to fix when you record the current settings and test one change at a time.
Start by checking domain expiry, nameservers, A records, CNAME records, DNS propagation and whether the domain points to the correct hosting service.
A domain is the address people type to reach your website, but it does not host the website itself. It needs to point visitors to the correct hosting server using DNS records.
If the domain registration expires, nameservers change, DNS records are removed or the wrong IP address is used, visitors may see an error, an old website, a parking page or nothing at all.
The key is to separate the domain from the hosting. A website can be perfectly healthy on the server, but still unreachable if the domain is pointing to the wrong place.
Most domain issues are caused by nameservers, DNS records, propagation, expiry or a mismatch between the domain and the hosting account.
Nameservers decide where DNS records are managed. If they point to the wrong provider, your DNS changes may not apply.
An A record points a domain or subdomain to an IP address, usually the hosting server.
A CNAME points one hostname to another hostname, often used for www or external services.
DNS changes can take time to update across networks, so some visitors may see old results temporarily.
If a domain expires, the website and email can stop resolving until the domain is renewed.
If the domain points to the wrong server IP, visitors may see the wrong website or an error.
First, confirm the domain is active and has not expired. If the domain is suspended, expired or still pending registration, DNS changes will not fix the website.
Next, check the nameservers. The nameservers tell the internet where to find your DNS records. If the nameservers point to the wrong place, you may be editing DNS in one control panel while the live domain is using another.
After that, check the key DNS records. The A record should point to the correct hosting IP address, CNAME records should point to the right destination, and MX records should remain correct if email is handled separately.
| Problem | What It Usually Means | What To Check |
|---|---|---|
| Domain expired | The domain registration is no longer active. | Check renewal status with the registrar. |
| Wrong nameservers | The domain is using the wrong DNS provider. | Compare registrar nameservers with the intended DNS host. |
| Incorrect A record | The domain points to the wrong server IP. | Check the hosting IP and A record value. |
| Missing CNAME | www or another hostname may not resolve correctly. | Check www and subdomain records. |
| Propagation delay | Some networks still see old DNS records. | Use a DNS propagation checker and wait for updates. |
| Email stopped working | MX or mail authentication records may have changed. | Check MX, SPF, DKIM and DMARC records. |
Nameservers and DNS records are often confused. Nameservers decide where DNS is managed. DNS records are the individual settings inside that DNS zone.
If the nameservers are wrong, changing an A record or CNAME in the wrong control panel will not affect the live domain. Always confirm the active nameservers before editing records.
A domain can use one DNS record for the website and separate records for email. Changing nameservers or replacing DNS zones without copying email records can break mailboxes even if the website starts working.
Before moving DNS, check MX, SPF, DKIM and DMARC records so email continues to send and receive correctly.
After DNS changes, some visitors may see the new website while others still see the old result. This is usually propagation rather than a new fault.
During this period, avoid repeatedly changing records. Multiple changes can make troubleshooting harder and extend confusion.
The biggest mistake is changing too many records at once. Domain issues need a clear order of checks, otherwise it becomes difficult to know which change caused the result.
Visitors do not see nameservers or DNS records. They only see that the website fails to load, shows the wrong page, displays a browser warning or sends them to an old hosting account.
Domain problems can also affect email. If MX records are missing or changed incorrectly, customers may not be able to reach you even if the website itself is working.
Keep a record of your registrar, active nameservers, website IP address and email DNS records. This makes future migrations and troubleshooting much easier.
Renew domains early, avoid last-minute DNS changes and take screenshots or exports of DNS zones before moving providers.
The domain is using nameservers from an old provider, so changes made elsewhere do not apply.
The domain points to the wrong IP address and loads an old website or server error.
The website works, but email stops because MX records were not copied during a DNS change.
Some DNS changes can interrupt both the website and email. Make sure you understand the purpose of each record before editing or deleting it.
Before changing hosting or rebuilding the website, confirm whether the domain points to the correct nameservers and server IP address.
Check domain expiry, nameservers, A records, CNAME records, propagation and email DNS before making further changes.
If you are replacing or registering a new domain, choose an extension that fits the website before connecting DNS and hosting.
Common causes include expired registration, wrong nameservers, incorrect DNS records, propagation delays or the domain pointing to the wrong hosting service.
Check whether the domain is active, then review nameservers, DNS records, propagation and hosting IP address.
Nameservers tell the internet where the DNS records for your domain are managed.
An A record points a domain or subdomain to an IP address, usually your hosting server.
A CNAME points one hostname to another hostname, often used for www or third-party services.
Some DNS changes appear quickly, but full propagation can take longer across different networks.
Yes. If the domain expires, the website and email may stop resolving correctly.
MX, SPF, DKIM or DMARC records may be missing or incorrect after the DNS change.
Yes. If the domain points to the wrong server, the SSL certificate may not match or load correctly.
Renew domains early, document nameservers, export DNS records and avoid changing multiple records at once.
If your domain still is not working, collect the domain name, current nameservers, DNS records, hosting IP address and the exact error visitors see.
Check whether the domain is active, whether DNS is being edited in the correct place and whether the domain points to the right hosting account.
If email is also affected, check MX, SPF, DKIM and DMARC records before making more website changes.
Add Website Hosts UK to your device
Install for quick access to hosting, tools, billing and support.