Member Avatar for Drycola

Hi,

I had an account on http://freedns.afraid.org where I redirect a short URL to my website.
I tried to open my website URL but it does not open, I tried to open the freedns.afraid.org but it doesn't open either. Does anyone know what is the problem?? Is it in my internet connection or its a global problem????

  • 3 Contributors
  • 2 Replies
  • 106 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by divisor

Dani AI

Generated

Given 's report that a short redirect stopped resolving and 's note that it worked from their machine, the pattern points to a DNS-resolution difference (local/ISP cache or resolver) or intermittent nameserver problems on the provider side. 's suggestion to try a different service is a sensible fallback, but first run a few targeted checks so the cause is clear before migrating.

Run quick lookups from your machine and from public resolvers to compare results (replace example.com with your short name):

nslookup example.com
nslookup example.com 8.8.8.8
nslookup example.com 1.1.1.1
dig +short NS example.com
dig @<one-of-the-ns> example.com A
curl -I http://example.com

How to read the outcomes: if no resolver returns an A record, the nameservers or the DNS provider are likely the issue. If public resolvers (8.8.8.8 / 1.1.1.1) show records but your ISP resolver does not, you are looking at caching/propagation or an ISP-specific problem. If DNS resolves but HTTP returns errors, the redirect/web server is at fault.

Immediate remediation steps: flush your local DNS cache (ipconfig /flushdns on Windows; sudo killall -HUP mDNSResponder on many macOS versions; sudo resolvectl flush-caches or restart nscd on Linux), try switching your machine/router to a known public resolver (Google 8.8.8.8 or Cloudflare 1.1.1.1), and reboot the router if the ISP caches aggressively. For quick testing only, a hosts-file entry can confirm whether the webserver itself responds, but do not use that as a permanent fix.

For a global view and authoritative-checks use tools such as IntoDNS and DNS Checker to inspect NS, SOA and propagation. If the provider is confirmed unstable, lower TTLs before switching, verify any dynamic-update clients are still authenticating, and contact the provider’s status/support with the diagnostic output you gathered.

Member Avatar for plumsauce

fyi, at the time of this post it seems accesible from my local machine.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.