By Khanh Tran
Hi there,
I’ve changed the DNS redirect for my domain, data.helixtap.com, redirect to a new IP address. However, I’m now getting a connection refused error when trying to access it. Can you help me identify and resolve the problem?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hey there! 👋
Your site is loading fine now! The issue you experienced might have been due to DNS caching, which can take 24-48 hours to propagate fully after changing DNS records.
During this time, some users might see the old IP or get connection errors.
If you still experience issues, try clearing your local DNS cache or testing with a different network.
- Bobby
Heya,
Bear in mind that a change in the DNS can take up to 48 hours to propagate. It’s always good to note that, also making the TTL lower might help you out as well.
Heya, @khanhtn
As the others mentioned the DNS propagation time can take up to 48 hours (sometimes even more) this is due to DNS cache from the ISPs. However it usually happens a lot faster.
You can use site tools like WhatsMyDNS to inspect the DNS update throughout different location around the world.
Regards
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.