Domain not pointing to hosting means your domain is not connected to your server. As a result, the website does not load or shows a default page.
This problem is almost always caused by incorrect DNS settings. The fix is straightforward once you identify where the domain is misconfigured: nameservers, the A record, the hosting account, or a propagation delay.
Quick Fix
- Check your domain nameservers.
- Verify the A record points to your server IP.
- Wait for DNS propagation (up to 24 hours).
- Clear DNS cache on your device.
- Confirm the hosting account is active and the domain is added.
Most cases are resolved by correcting DNS records or waiting for propagation.
What Does “Domain Not Pointing to Hosting” Mean?
This issue occurs when a domain name does not resolve to the correct server.
When someone enters your domain, DNS should direct them to your hosting server IP. If that mapping fails, the browser cannot load your website.
You may see:
- A blank page
- A hosting default page
- A DNS error such as ERR_NAME_NOT_RESOLVED
- Another website entirely
This means DNS is not correctly configured, or the domain is not added to the hosting account.
Why This Happens
Incorrect Nameservers
If your domain points to the wrong nameservers, DNS records from your hosting provider are ignored. The registrar must point to the nameservers that actually hold your zone.
Wrong A Record
The A record must point to your server’s IP address. If it points elsewhere, the site will not load, even if nameservers are correct.
DNS Propagation Delay
After changing DNS, updates can take time to spread globally. The domain may work in some locations and fail in others during that window.
Hosting Not Linked to Domain
The domain must be added inside your hosting panel as the primary or an addon domain. If it is not added, the server has nowhere to serve the files from.
Expired Domain
If the domain is not active, it cannot resolve at all.
DNS Cache Issues
Your device, router, or ISP may store an outdated DNS answer.
Step-by-Step Fixes
1. Check Nameservers
Go to your domain registrar and ensure the nameservers match your hosting provider.
Example:
ns1.hostinger.com
ns2.hostinger.comIf they are incorrect, update them. Changing nameservers is a larger change than editing a single A record and can take longer to propagate.
2. Verify the A Record
Open DNS settings and check:
- Type: A
- Name: @
- Value: your server IP
This record connects your domain to your server. Also check the www record so both versions point to the same place.
3. Add the Domain to Hosting
In your hosting panel:
- Add the domain as primary or addon domain
- Assign the correct directory
If it is not added, the server will not serve your site even when DNS is perfect.
4. Wait for DNS Propagation
Changes can take up to 24 hours. During this time the domain may work in some locations but not others. Do not keep changing records while waiting, or the clock resets.
5. Flush DNS Cache
Windows:
ipconfig /flushdnsmacOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder6. Test Domain Resolution
nslookup yourdomain.comIf no correct IP appears, DNS is not configured properly. Compare with nslookup yourdomain.com 1.1.1.1 to see whether only your local resolver is stale.
Advanced Troubleshooting
Check DNS Globally
Use an online DNS propagation tool to confirm the records worldwide. If most locations show the correct IP, remaining failures are usually local cache.
Verify Hosting IP
Ensure your server IP has not changed. Hosts sometimes migrate accounts to a new address without updating the zone.
Check CNAME Records
Incorrect CNAME settings may override A records, especially on www. A CNAME and an A record cannot coexist on the same name.
Disable CDN Temporarily
If you use Cloudflare or another CDN, a wrong proxy status or stale record can block resolution. Pause the proxy and test the origin IP directly.
Does This Affect SEO?
Yes, significantly. If your domain does not point correctly, Google cannot crawl your site, pages can be removed from the index, and traffic drops. Fix DNS issues immediately to avoid ranking loss.
How to Prevent This Issue
- Keep DNS settings documented
- Double-check changes before saving
- Use a reliable hosting provider and registrar
- Monitor domain expiration
- Avoid frequent DNS changes
When to Contact Support
Contact your provider if DNS changes do not propagate, nameservers do not update, or the domain still does not resolve after 24 hours. Your registrar or host can verify the zone and registration status.
Related DNS Errors
FAQ
Why is my domain not pointing to my hosting?
Usually because of incorrect nameservers, a wrong A record, or the domain not being added to the hosting account.
How long does DNS propagation take?
Typically a few minutes to 24 hours.
Can I fix this without hosting support?
Yes. Most issues can be fixed by updating nameservers or the A record.
Does this affect SEO?
Yes. Search engines cannot access your site if DNS is broken.
Can a wrong A record cause this?
Yes. If it points to the wrong IP, your site will not load.
Summary
Domain not pointing to hosting happens when DNS does not direct your domain to the correct server.
The most common causes are incorrect nameservers, a wrong A record, a missing domain in the hosting panel, or a DNS propagation delay. Fix the records, confirm the domain is added to hosting, and wait for propagation. That usually resolves it.
Main Error Hub
For a full list of DNS, SSL, server, and WordPress issues, see the complete website error guide.