DNS Resolution Error
The domain you’re trying to reach cannot be found
Almost 24 years have passed and there is no access to the site. DNS A-record is everywhere on the servers, check for help https://dnschecker.org/#A/churbachky.kesug.com. Spend some money now.
Given that Neither InfinityFree nor IFastNet are 24 years old, and the .kesug.com domain was registered by infinityfree in 2023 (according to whois) I’m going to assume you mean 24 days?
But either way that’s not relevant. Unless you mean 24 hours. In which case, you may need to wait for up to 72 hours for it to be available everywhere.
When visiting your site I get a 403 error.
This would suggest that if you’re getting a DNS error (and its been more than 72 hours since you set up the site) then it’s likely a local DNS block either from a firewall\virus scanner or your ISP blocking it.
To fix the 403 error make sure you’ve got an index.php or index.html file, and that you’ve not got any broken blocking rules in your .htaccess file.
Honestly, you’re not in a position to demand anyone spends money to help with a problem on FREE hosting, which doens’t even look like a problem with the hosting service
It’s been almost 24 hours and the site is still down. The DNS A record is everywhere on the servers, checked with https://dnschecker.org/#A/churbachky.kesug.com. Please do something.
As I said above, DNS resolution can take up to 72 hours. That site you’ve linked doesn’t check all DNS providers.
As for the error page, you’ve got that looks like the one provided by Ifastnet. Please make sure that the domain is correctly added to your account.
What do you expect us to do here? You verified it yourself with dnschecker.org: your domain is fully setup and the DNS record for your domain is active. It’s strong evidence to suggest that the issue is something specific to you, not your website.
As for why it doesn’t work for you, the reason is very obvious. The client area tells you what’s wrong, and so does the page you are being redirected to:
It can take up to 72 hours for your website to start working. Saying “it’s been almost 24 hours” tells me that your website was set up less than 24 hours ago, meaning that your website not yet working everywhere is completely normal, and no cause for concern.
Let’s assume you don’t know the reason either. The magic 72 hours, the mysticism.
You probably work here as administrators, part-time, assistants.
A few things I want to clarify here.
I don’t know the reason either because I cannot reproduce the issue. As far as I can tell, nothing is wrong with your website. You claim your website is not working for you but I have no way to verify that or see what’s actually happening inside your browser or network.
The 72 hours is not a magic number of hard boundary. We publish our DNS records with a so-called Time-To-Live of 24 hours. That means that clients are instructed to remember records for 24 hours. However, clients are free to remember records for longer or shorter than that. And add to that that there may be multiple levels of DNS cache (e.g. your ISP, your router and your computer all having DNS cache), and how those caches talk amongst each other can vary, and bad configuration or bad luck can make it take longer than 24 hours.
Most providers working with DNS say something between 48 and 72 hours for changes to take effect. It often takes less time than that, but sometimes it takes more time. It’s just a wide margin to help us avoid chasing configuration issues that don’t exist and we cannot resolve.
Finally, everyone here except for me is a community volunteer. They are not staff, they are not paid to do this, and they don’t have any system access. They are simply helping you out of their free will using their own knowledge and experience.
Actually I work for Experian uk&I as a full time business analyst. I volunteer my time here helping people like you who are experiencing problems.
There’s no reason to be rude.
