Intermittent DNS Resolution Failure for Lorehaven Website

Website URL

https://lorehaven.great-site.net

Error Message

DNS_PROBE_FINISHED_NXDOMAIN

Other Information

The website resolves successfully through Google Public DNS. My Android phone can access it when Google Private DNS is enabled and set to dns.google, but it fails to resolve when using the default DNS configuration.

Some devices and networks fail with DNS_PROBE_FINISHED_NXDOMAIN, while Google Public DNS (8.8.8.8) resolves it correctly to 185.27.134.214, and an external checker received HTTP 200.

I have not changed my WordPress files, website content, image URLs, or hosting configuration to troubleshoot this issue.

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 your results, this sounds like your network’s default DNS server giving wrong answers, not a fault with the domain. Our article on this error describes it. Free subdomains can be filtered by some internet providers and networks, and their DNS servers answer “not found” for blocked domains. The article says we can’t see these blocks from our side. Reports from users are how we find out where they happen.

Your own tests fit that. Google DNS returns the right IP, your external checker got a 200, and only your default resolver fails. The Cloudflare timeouts are probably your network blocking outside DNS servers. The article says some networks do this, so it doesn’t point at Cloudflare or at our nameservers.

Two things would settle it:

  1. What does dnschecker.org show for lorehaven.great-site.net with record type A? If most locations show the IP, the domain works worldwide and the problem is on your network’s side. If some locations fail, that’s a different situation.
  2. Which internet provider and country is the failing connection (your Windows PC and your Android phone on its default DNS)? The article asks for this so reports can be matched to a provider.

Thank you. I have already confirmed that Google Public DNS resolves lorehaven.great-site.net to 185.27.134.214, while my Windows computer’s default DNS resolver fails. My Android phone also accesses the website when Google Private DNS is set to dns.google, but fails with its default DNS configuration.

The affected connection is in Nigeria. I will check DNSChecker’s A-record results and share what they show.

Could you also clarify whether InfinityFree has documented cases of Nigerian internet providers filtering its free subdomains, and whether there is a recommended way to confirm this with the affected provider?

I had AI summarize your post. It’s EXTREMELY long, seems AI written, and the information density seems rather low (I lost track of how many times it repeated that resolving with Google DNS works). Longer doesn’t mean better. Please check and read your message yourself before posting next time, and if that’s too much work because it’s so long, maybe consider that your post might just be too long.

I didn’t read your entire post, I’m going by the summary.

I checked your domain and it’s resolving fine from here. dnschecker.org shows green across the board.

Yes, there have been a number of reports from Globacom customers who are unable to access their websites on their hosting. I think that Globacom is blocking the great-site.net domain.

Thanks for checking, and sorry for the overly long post. Since DNSChecker shows the domain resolving from your locations, while it fails on my default DNS configuration but works with Google Public DNS, I’ll investigate whether my network provider is filtering the free subdomain. Have you seen this happen with Nigerian ISPs, and is there a specific way to confirm it?

Like I said:

Your current evidence already strongly points in that direction. You could try to verify it with other people on the same connection, or by using a different connection where you also use the default resolver.