The website is not opening in my browser. Chrome shows:
Hmmm… can’t reach this page
Check if there is a typo in sevamedmart.rf.gd.
DNS_PROBE_FINISHED_NXDOMAIN
However, my InfinityFree control panel does not show any issues with the hosting/account.
I have already checked the domain name and it appears to be correct. Could someone please check whether the subdomain sevamedmart.rf.gd is properly connected to my InfinityFree hosting account and whether there is a DNS/nameserver issue?
Please let me know if I need to change anything in my DNS settings or hosting configuration.
Maybe, ISP is blocking , because from past few days, when I am accessing any domain under rf.gd , sometimes i get this problem too, then after 1 minutes , it automatically get resolved, this interruption occur at any time and then fixed on its own. Moderator may know better answer, wait till they respond.
Your domain name is reachable from all over the world, so I think the problem is something specific to you.
This could be caused by antivirus software of a firewall on your own computer, or something on your network, either setup by your network administrator or your ISP.
In any case, the next step is to narrow down where the block is coming from. Do you experience the same issue on a different device? Or on a different network? Are you able to bypass it on a VPN? That should get you closer to finding the cause so you know where you need to go to fix this.
Thank you for the response. I have already performed extensive testing across multiple devices and networks, and the issue is specifically isolated to the Reliance Jio network in India (affecting both JioFiber broadband and Jio mobile data), which handles roughly half of the country’s internet traffic.
The site resolves perfectly on other networks (like Airtel and Vi) and via public resolvers like Google DNS (8.8.8.8). It also opens instantly when using a VPN.
However, running a deep DNS diagnostic via DNSViz reveals that this isn’t a random local firewall or antivirus block. It is a structural DNS configuration issue with the free subdomain infrastructure itself. The report shows a Lame Delegation / Nameserver mismatch between the parent registry zone and your authoritative cluster:
Strict, RFC-compliant ISPs like Jio drop queries immediately and return a hard NXDOMAIN when they encounter a mismatched delegation chain like this, whereas more forgiving resolvers like Google DNS ignore the error.
I’ve never heard of anything like this. Do you have any official information supporting this?
Because a DNS resolver doing this sounds completely backwards.
Think about it: the purpose of a DNS resolver is to resolve DNS. When you request an IP address, it should ask the configured nameservers for this IP address, and return that to the client.
The DNS resolver you describe would need to request that IP address, then additionally request the NS records of the nameservers, and when it sees they don’t match, it then discards the IP address it obtained from an authoritative nameserver because it didn’t return the desired data for a different query.
Yes, our setup isn’t fully RFC compliant. But I’ve never heard of this being a problem, and we generally focus on issues with actually tangible benefits over complying to best practices for the sake of being compliant.
