DNS Not Updating After Adding Hosting? Fix It

If your domain is not resolving to your new hosting after you added it, the cause is almost always a mismatch between the nameservers or DNS records at your domain registrar and the ones your hosting provider gave you. The fix is to log into your registrar, update the nameservers or A record to match your host’s details, then wait for propagation (up to 48 hours) and clear your local cache.

How DNS Works (and Why It Takes Time)

DNS (Domain Name System) is the internet’s phonebook. When you type your domain, your browser asks a DNS resolver (usually run by your ISP or a public service like Google) for the IP address. That resolver checks a chain of servers: root, TLD (like .com), and then your domain’s authoritative nameservers. Your hosting provider gives you nameserver addresses (e.g., ns1.yourhost.com) or an IP address for an A record. Until the resolver’s cached copy expires (TTL), it will keep sending visitors to the old server.

Propagation is the time it takes for this update to spread across all resolvers worldwide. It can be minutes or up to 48 hours, depending on the TTL set before you made changes and how quickly each resolver checks back. You can check your current DNS using tools like nslookup or online lookup services, but remember they may show cached data.

Step-by-Step: Find the Fault

1. Check your hosting welcome email – It should contain either two nameserver addresses (like ns1.host.com and ns2.host.com) or a specific IP address for the A record.
2. Log into your domain registrar (where you bought the domain, e.g., GoDaddy, Namecheap, Google Domains). Find the DNS management or Nameservers section.
3. Compare what’s there – If it shows old nameservers, replace them with the ones from your host. If it shows an A record, make sure the IP matches your host’s IP.
4. Save and wait – Changes are not instant. Wait at least 15 minutes before checking again.
5. Clear your local cache – On Windows, run ipconfig /flushdns in Command Prompt. On macOS, use sudo dscacheutil -flushcache.

Common Mistakes That Cause Delays

• Wrong nameserver spelling – A single typo will break resolution. Copy-paste from your host’s email.
• Changing A record instead of nameservers – If your host uses shared hosting, they often require nameserver changes, not an A record. Using an IP for a shared server can point to the wrong site.
• Forgetting to update the www record – You may need both the bare domain (example.com) and the www subdomain to point to the same place.
• Old TTL values – If your previous DNS had a TTL of 86400 (24 hours), it will take a full day for many resolvers to refresh. Lower the TTL before making changes if you can.
• Registrar vs. host confusion – Your domain may be registered with one company and hosted with another. DNS changes happen at the registrar, not the host.

How to Verify the Fix

After updating, use a global DNS checker (like dnschecker.org) to see if the new records appear worldwide. If they do but your browser still shows the old site, clear your browser cache or try a different device. If the checker shows mixed results, wait longer. If it shows no change after 24 hours, double-check your registrar’s settings – sometimes there is a separate “DNS Hosting” vs. “Domain Name Servers” field.

If you changed nameservers, you can also check the authoritative servers with dig NS example.com (on Linux/macOS) or nslookup -type=NS example.com (on Windows). If those return your host’s nameservers, the DNS is correct; the issue is local caching.

When to Contact Support

If you have followed all steps and waited 48 hours, contact your hosting provider’s support first. They can verify that your domain is active on their server. Then contact your registrar if the host confirms everything is fine. Provide them with the exact steps you took and the output of your DNS checks. Do not expect instant fixes – support agents will also need to wait for propagation.

Preventing Future DNS Issues

• Keep DNS records documented – Save a copy of your old records before making changes, so you can revert if needed.
• Use a low TTL (300–600 seconds) – When you plan to move hosting, lower the TTL a day before the change. This makes the update propagate faster.
• Use the hosting provider’s nameservers – If you are not comfortable managing DNS, using their nameservers is simpler than updating A records manually.
• Set up email records – If your email is hosted elsewhere, you may need to update MX records after changing nameservers. Check your host’s documentation for the correct values.

Frequently Asked Questions

Why is my DNS still not updated after 48 hours?

If more than 48 hours have passed, the issue is likely a typo in the nameserver or A record, or the registrar has not propagated the change to the TLD servers. Double-check the exact spelling and that you are editing the correct domain. Some registrars have a separate “DNS Hosting” section that overrides nameservers – make sure you are not using that.

Should I change nameservers or A record?

It depends on your hosting plan. Shared hosting and cPanel hosts usually require you to change nameservers to theirs. VPS or dedicated servers often provide a single IP, so you update the A record. Check your host’s welcome email or documentation.

How long does DNS propagation actually take?

Most changes propagate within 1-4 hours, but the official maximum is 48-72 hours. It depends on the TTL set before the change and how often resolvers refresh. Some ISPs are slower than others.

Can I speed up DNS propagation?

No, you cannot force all resolvers to update instantly. However, you can lower the TTL before the change, use a public DNS like Google (8.8.8.8) to check, and clear your local cache. You can also use a VPN to test from a different location.

Why does my website work on my phone but not on my PC?

This is a caching issue. Your phone and PC use different DNS resolvers. The one your phone uses may have already updated, while your PC’s ISP resolver still has the old cached record. Flush your PC’s DNS cache or wait a bit longer.

What if I see my new site on a DNS checker but not in my browser?

Your browser has its own DNS cache. Clear it by going to the browser settings or restarting the browser. Also, try a private/incognito window – it often bypasses the cache.

Related

• Shipping Cost vs Quote: Reconcile Carrier Bills
• Can Teachers See Your Screen on Zoom? Truth
• Set Up Channel Points on Twitch: Full Guide