This guide helps you troubleshoot when your domain still isn't working after 48 hours of making DNS changes.
Check Your Domain Status in Web60
Log into your Web60 dashboard and go to the Domain page. Look at the status indicator next to your domain name. If it shows "Connection Failed" or similar, there's definitely an issue that needs fixing.
The status will tell you whether Web60 can reach your domain properly. A green "Connected" status means the technical connection is working, even if you're still having problems accessing your site.
Run DNS Diagnostics
Use the Web60 DNS checker at web60.ie/tools/dns-checker to test your domain. Enter your domain name and check either:
- A records if you set up DNS using A records
- NS records if you changed your nameservers
For A records, the tool should show the IP address 80.93.24.138. For nameserver records, you should see ns1.web60.ie and ns2.web60.ie listed.
If the DNS checker shows different information, your changes haven't taken effect yet or weren't saved properly.
Check Your Domain Registrar Settings
Log into your domain registrar account (where you bought your domain). This might be SmartHost, GoDaddy, Namecheap, or another company.
Verify that your changes were actually saved:
- For A record setup: Check that you have an A record pointing to 80.93.24.138 on the @ symbol (not on www or another subdomain)
- For nameserver setup: Confirm the nameservers are set to ns1.web60.ie and ns2.web60.ie with no typos
Make sure you clicked "Save" or "Update" after making changes. Some registrars require you to confirm changes via email.
Common Problems and Solutions
Wrong IP address: The A record must point to exactly 80.93.24.138, not any other IP.
A record on wrong subdomain: The A record should be on @ (the root domain), not on www or any subdomain.
CNAME instead of A record: If you see a CNAME record, delete it and create an A record instead.
Cloudflare proxy enabled: If you use Cloudflare, the cloud icon next to your DNS record must be grey (DNS only), not orange (proxied). This is the most common cause of connection failures.
Domain expired: Check your domain hasn't expired at your registrar. Expired domains stop working immediately.
Transfer lock active: Some domains have transfer protection that blocks DNS changes. Check with your registrar.
Special Cases
.ie domains can take up to 72 hours to update, longer than other domain types.
Wrong domain entered: If you accidentally entered the wrong domain in your Web60 portal, cancel the current domain connection and submit the correct domain again.
Normal DNS propagation takes 1-24 hours for A records and 24-48 hours for nameserver changes, but these are maximum times - most changes work much faster.
If you've checked everything above and your domain still isn't working after 48 hours, contact Web60 support with your domain name and the results from the DNS checker tool.
Frequently asked questions
How long should DNS changes take to work?
A record changes typically take 1-24 hours, while nameserver changes take 24-48 hours. Irish .ie domains can take up to 72 hours.
What IP address should my A record point to?
Your A record must point to exactly 80.93.24.138 for Web60 hosting.
Can I use both nameservers and A records?
No, choose one method. Either change your nameservers to ns1.web60.ie and ns2.web60.ie, or keep your current nameservers and add an A record.
Why does Cloudflare stop my domain from working?
Cloudflare's orange cloud proxy interferes with Web60's connection. Set the cloud icon to grey (DNS only) instead.
My registrar shows the changes but the DNS checker doesn't. Why?
DNS changes take time to spread across the internet. Wait a few more hours and check again, especially for .ie domains.
What should I do if I entered the wrong domain?
Cancel the current domain connection in your Web60 dashboard and resubmit with the correct domain name.
How do I know if my domain has expired?
Log into your domain registrar account and check the expiry date, or use a domain checker tool to verify the status.
Last updated: 26 March 2026
