Safari cannot open the page because the server cannot be found.
The issue occurs when accessing the website using mobile data on both Maxis and U Mobile networks in Malaysia. The website becomes accessible when using a VPN or Cloudflare DNS (1.1.1.1).
Google Public DNS has also returned SERVFAIL for the domain.
Other Information
My website is hosted on InfinityFree, and the domain’s A record points to 185.27.134.221.
The website and its database are working correctly when accessed through a PC, BlueStacks, or a VPN.
However, DNSChecker shows inconsistent DNS resolution across different locations:
Germany, Mexico, Australia and New Zealand resolve to 185.27.134.221.
Malaysia (Port Dickson) and Brazil fail to resolve.
A resolver in Singapore returns 0.0.0.0.
I have tested the website on two different mobile networks (Maxis and U Mobile), and both experience the same issue without a VPN.
Could you please investigate whether there is a DNS resolution issue affecting this free subdomain or its authoritative nameservers?
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.
Could you run nslookup dunpelabuhanklang.page.gd on a device that’s failing, using the network’s default DNS. Then run nslookup dunpelabuhanklang.page.gd 8.8.8.8 and post both outputs in full. I need them to see whether the failure is the resolver returning SERVFAIL, returning nothing, or timing out. They’ll also show which nameserver it was talking to.
It would also help to know roughly when you first saw the failure and whether it comes and goes. A resolver that fails once and then works is a different problem from one that fails every time.
I searched the forum and knowledge base and found nothing that explains a free subdomain failing on only some networks, so I don’t have a cause to give you yet.
The issue started on November 2, 2026 (Malaysia time, UTC+8).
Previously, the website was inaccessible on iPhones using Maxis and U Mobile mobile data without a VPN. However, it worked when using a VPN or Cloudflare DNS.
Google Public DNS previously returned SERVFAIL, and DNSChecker showed inconsistent results across different locations.
The website has now become accessible without a VPN, so the issue appears to be intermittent.
I will run the requested nslookup tests if the issue occurs again and share the full results.
We had an outage a few hours ago in our nameservers in the US West coast. Since our nameservers don’t have any locations in Asia, requests from east Asia are often routed to the US West location too. So that could explain any DNS errors you had before.
However, that issue was solved already. Are you able to access your website now?