This article explains DNS propagation and how long different types of domain changes take to spread across the internet.
What is DNS Propagation?
DNS propagation is the process of DNS changes spreading across servers worldwide. When you change your domain settings, these changes don't happen instantly everywhere. Different servers around the world need time to receive and cache the new information.
Think of it like updating a phone book. When someone changes their phone number, it takes time for all the phone books around the world to get updated with the new number.
How Long Different Changes Take
DNS Records Changes in Web60 Portal
When you change DNS records through your Web60 dashboard:
- Changes appear on Web60's servers (ns1 and ns2) within 60 seconds
- External servers may take up to 1 hour to see the changes
This is because other servers cache (temporarily store) DNS information for up to 3600 seconds (1 hour). This cache time is called the TTL (Time To Live).
Connecting Domain via A Record
If you're connecting your domain to Web60 using A records, changes typically take 30 minutes to 24 hours to propagate fully.
Changing Nameservers
When you change your domain's nameservers:
- Most domains: 1 to 48 hours
- .ie domains: Sometimes up to 72 hours
Nameserver changes usually take longer because they're a bigger change that affects how your entire domain is handled.
How to Check DNS Propagation
To see if your changes have spread globally:
- Use Web60's DNS checker at web60.ie/tools/dns-checker
- Enter your domain name
- Check the results from different locations
You can also use dnschecker.org to see results from servers worldwide.
Important Things to Remember
Don't keep changing records during propagation. Each time you make a change, it resets the TTL and starts the propagation process over again. Make your changes once, then wait.
Browser cache is separate from DNS cache. If you can't see your changes, try clearing your browser cache or opening your site in a private/incognito window.
Your computer caches DNS too. To flush your local DNS cache:
- Windows: Open Command Prompt and type
ipconfig /flushdns - Mac: Open Terminal and type
sudo dscacheutil -flushcache
If your custom domain isn't working after the expected propagation time, there may be a configuration issue that needs checking.
If you're still stuck, raise a support ticket and we'll check your DNS settings for you.
Frequently asked questions
Why is my domain still not working after 24 hours?
There may be a configuration error with your DNS settings. Check your domain connection status in your Web60 dashboard or contact support for help.
Can I speed up DNS propagation?
No, you cannot speed up propagation as it depends on servers worldwide updating their cached information. The process takes as long as it takes.
My website works in some locations but not others. Is this normal?
Yes, this is normal during DNS propagation. Different servers around the world update at different times, so some locations may see your changes before others.
What happens if I keep changing my DNS records?
Each change resets the propagation timer, meaning it takes longer for changes to spread globally. Make your changes once and wait for propagation to complete.
Why do nameserver changes take longer than other DNS changes?
Nameserver changes affect how your entire domain is handled, not just individual records. This bigger change requires more time to propagate across all DNS servers.
Will my website be down during DNS propagation?
Your website should remain accessible during propagation, though some visitors may see the old version while others see the new version until propagation completes.
How do I know when DNS propagation is complete?
Use a DNS checker tool to see if your changes appear consistently across different global locations. When all locations show your new settings, propagation is complete.
Last updated: 26 March 2026