I have already tried using different DNS servers, flushing my DNS cache, testing through mobile data, and checking DNS propagation using DNSChecker.org.
DNSChecker shows results pointing to my hosting IP, but my direct DNS queries still return NXDOMAIN.
My index.html file is already uploaded to the htdocs folder.
Please help me check if my subdomain is correctly registered and configured on your DNS servers.
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.
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.
Going by what you describe, the domain itself looks fine, and the problem is somewhere between you and the internet. Our article on this error says that if dnschecker.org shows your domain working worldwide but your browser can’t find it, the answer is wrong on your device or network. It also says that blocking by internet providers is most common with free subdomains.
Can you tell me your internet provider and country, and paste the output of these two commands, run on the same connection that fails?
If the first one fails and the second returns an IP, your provider’s DNS is filtering or serving stale answers. If both fail but dnschecker.org works, your network may be blocking outside DNS servers. Your provider and country matter because the article says blocks like this can’t be seen from our side, so user reports are how they get tracked.
Here’s the article, which also covers switching to a public DNS server:
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.
Could you run your domain through dnschecker.org with the record type set to A and tell me whether most locations show a green check with an IP or a red cross? That tells us whether the domain isn’t resolving for anyone, or whether only your networks are getting a “not found” answer. Please also tell me your internet provider and country.
Your hosting account was created less than 72 hours ago. Our article on this error says new domains can take that long to work everywhere, and some locations may fail until then. This could be that. Two different networks failing fits it too, if both use DNS servers that haven’t picked up the domain yet.
The article on this error is here:
The article on new domains that aren’t working yet is here:
If dnschecker shows the domain working in most places, the same article explains how to compare your normal DNS server with a public one. It uses nslookup seacco-coopstii.wuaze.com and nslookup seacco-coopstii.wuaze.com 1.1.1.1. Post the output of both if you run them.
I’m sorry, but there is nothing I can do for you here.
We’re your hosting provider, so the only thing we can do for you is to make sure that our hosting works. As your own tests have shown: your website itself is setup correctly.
My best guess at this point is that your ISP is blocking access to your website. And that’s where my control ends. I don’t know your ISP, I don’t know if, how or why they block certain websites, and I have no way to check that from my end.
Your internet provider is responsible for giving you a working internet connection, and if an issue on their is preventing you from reaching your website’s that’s a problem with your internet connection.
Which means that the next step is to contact your internet provider about this, because they should check why their connection is not correctly resolving your domain name.