Can a domain be broken. If yes, how do you deal with it?

May 15, 2015 910 views
DigitalOcean Miscellaneous Ubuntu

I've had some issues with one of my domains,, for a while now. The problem is that it's inaccessible for certain IP addresses (depending on where you live). I've been changing both registrar and server provider two times the past year, but it hasn't solved the issue. Right now, it's on the same registrar as one of my other domains ( It's set up on the same server on DigitalOcean using the exact same configuration. Yet, the IP addresses that couldn't access the website before still seem to be blocked somehow.

I've been troubleshooting with both registrar and earlier server provider but it hasn't been solved. What is going on?

4 Answers

Hello, do you have any server logs showing information on the blocked IP's? Would it be possible to have someone who is being blocked run a network test? It is hard to pinpoint where the problem is without some additional information.

I'm being blocked right now. Tracerouting gives me "unknown host".

  • It works.. :D from my end..

    Anyway, judging from your description, its highly unlikely that it is a DNS issue, unless you have some CDN proxy (like cloudflare) ..

    It seems its an internal software issue of your end. Check Firewall or any other software that may have blocking feature for traffic filter.. Also in case you are changing server, allow 72 hours for DNS to propagate through out the internet before drawing any conclusion..

    By the way, do consider other two possibility since the same IPs are effected,

    1. The user is having some issue with in local machine (some firewall or blocking software or network issue)
    2. ISP of the effected users are blocking the domain..

The issue is not only on my own netword; many people from all around the world seem to not be able to access - while some are. It's a really strange problem. It's set up exactly the same as some other domains that ARE working using the same server. It's really frustrating.

I just solved it! Turns out there were some old DNSSEC values (that I haven't even configured) left. I removed it and now it seems to work!

Have another answer? Share your knowledge.