Both my web1337.net domains resolve to private IP 10.10.34.36 and are unreachable

Hosting Support
1

Website URL

http://storycollab.web1337.net/

Error Message

Hello,

I have a connectivity problem with two free subdomains on the same InfinityFree hosting account.

Account:
if0_39689522

Domains:

The InfinityFree dashboard shows the hosting IP as:
185.27.134.205

However, both domains resolve to the private IP 10.10.34.36, even when using public DNS servers.

DNS test with Cloudflare:
nslookup storycollab.web1337.net 1.1.1.1

Result:
10.10.34.36

DNS test with Google:
nslookup storycollab.web1337.net 8.8.8.8

Result:
10.10.34.36

The second domain has exactly the same issue:
studyos.web1337.net → 10.10.34.36

HTTP connection also fails:

curl -I http://storycollab.web1337.net
→ Failed to connect to port 80

HTTPS also fails:

curl -I https://storycollab.web1337.net
→ Failed to connect to port 443

The same HTTP problem occurs with studyos.web1337.net.

Both domains are assigned to the same hosting account, and the InfinityFree dashboard reports:

Health Check: No issues found

The website files are present in the correct htdocs directory, including index.php.

Could you please check the DNS / virtual host configuration for these web1337.net subdomains?

It appears that the public DNS is resolving both domains to 10.10.34.36 instead of the hosting IP shown in the dashboard (185.27.134.205).

Thank you.

2

image
image1707×710 99.5 KB

they look to be working to me.

have you tried accessing your site from a different network?

the fact that its directing to 10.10.34.36 suggests that something on your network (maybe an over zealous firewall? or your ISP?) is blocking your domain and trying to redirect to you to an internal or holding page

3

This is my guess too.

The customary way to do this is to filter the DNS responses in the DNS resolver of your ISP, which you can then bypass by using Google’s or Cloudflare’s DNS server.

However, it is technically pretty straight-forward to hijack DNS traffic in a firewall and reroute or rewrite it, and apply blocking or filtering to it.

This is one of the reasons why protocols like DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT) exist.

dnschecker.org shows that all DNS resolvers they test return the right IP address (except one, but that one is known to be flaky): https://dnschecker.org/#A/storycollab.web1337.net

One web search result for that particular IP address referred to it being associated with a filtering firewall covering all internet traffic in Iran, which seems like it may be relevant to you.