Custom domain pointing to old IP / Health Check error after moving accounts

[xycun_dev]

Website URL

https://karyadigital.online/undangan/?i=1

Error Message

Your domain name is not pointing to our server! Your domain name is pointing to the IP address(es): 185.27.134.33. and 185.27.134.137 My current account IP is 185.27.134.166.

Other Information

Your domain name is not pointing to our server! Your domain name is pointing to the IP address(es): 185.27.134.33. My current account IP is 185.27.134.166.

[system]

Welcome to the InfinityFree community forum! Good to have you here.

• Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.
• Volunteers can’t see your account or website. Share what you actually see, like error messages and what happens when you try something. That’s more useful than your theory of what’s wrong.
• AI tools often get InfinityFree wrong. If a volunteer’s advice differs from what an AI told you, please try the volunteer’s suggestion first.
• Solving an issue is a joint effort. Try the suggestions you get and report back what happened.

[InfinityFreeBot]

Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.

The Health Check error means the DNS for karyadigital.online still returns 185.27.134.33 and 185.27.134.137. Your account’s IP is 185.27.134.166, so the domain isn’t pointing at it yet. I can’t tell from your post whether these are leftover records or a nameserver change that hasn’t spread.

The knowledge base article below says DNS settings are managed at your registrar or DNS provider, not with us. You can use InfinityFree’s nameservers, or keep your current nameservers and add the right DNS records there. The waiting time (up to 72 hours) only starts once those settings are correct, so a wrong setting won’t fix itself.

The Health Check section for the domain in the members area shows whether the nameservers point to us and, if not, whether the DNS records point to the right IP.

Why isn't my domain working yet?

You’ve just added a domain to your hosting account, or changed your domain’s nameservers. But when you visit it, you see a “DNS Resolution Error” page, a browser error saying the site can’t be found, or your old website instead of your new one. This is normal for a new domain. Most domains start working within 24 hours, but it can take up to 72 hours before a domain works for everyone around the world. How long it takes depends on things outside of our control, like your internet provider and y…

To narrow it down, I need two things:

• Are you using InfinityFree’s nameservers at your registrar, or your current nameservers with A records? If it’s A records, which IP is the domain’s A record set to?
• Roughly when did you last change the nameservers or records at the registrar?

If you did move the nameservers recently, old answers can linger. The article also covers flushing your DNS cache or switching to a public DNS server to check what your own device sees.

[xycun_dev]

Hello, thank you for the response. Here are the answers to your questions:

1. I am currently using my current registrar (Hostinger) with an A Record pointing to my new account IP (185.27.134.166), along with the required CNAME records.
2. I last changed and updated these DNS records just a few hours ago when I moved the domain to my new hosting account.

Regarding the IPs mentioned:

• The IP “185.27.134.33” is indeed correct because it was the IP of my old account before I deleted the domain and moved it.
• However, the IP “185.27.134.137” was NEVER used by me at all, but the system/bot keeps detecting it.

Even though I have updated my A Record to the new IP (185.27.134.166) in my Hostinger DNS settings, the InfinityFree Health Check still blocks it and points to the old IPs. Could you please help me force-refresh or clear this internal DNS cache on your end so my domain can connect to my new account?

Thank you!

[Meishin]

@xycun_dev

Could you please help me force-refresh or clear this internal DNS cache on your end so my domain can connect to my new account?

Read

@system

• Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.

So instead of asking for others to fix your issue, please follow this instead:

@system

• Solving an issue is a joint effort. Try the suggestions you get and report back what happened.

Now since your domain was moved from one account to another it still subject to DNS caching, which means that it’ll take sometime for it to work. And because DNS caching comes from whatever DNS resolver people may have, not us, there’s nothing we can “force-refresh” or “clear” because we don’t have access to those servers. The authoritive nameservers always update themselves immediately.

[Admin]

I checked your account and everything seems to be working fine: your domain is pointing to our servers, and our servers are returning the right IP address. However, it seems that the DNS check used by the Health Check is seeing some outdated cached DNS data. And that’s just the Health Check being wrong, it’s not a problem with your domain or our hosting.

This is more or less what can be expected after moving a domain name to a different account. It requires a DNS change which takes some time to be visible everywhere.