OpenDNS Running Out of Answers

Two days ago when PLDT MyDSL conked out on virtually all of us, I was having my own problems with my Bayantel DSL here in my office. I couldn’t access most sites I go to such as Google and Twitter. I thought maybe OpenDNS can solve that problem. True enough, it did!

Yesterday though, while I was trying to access my site,, the OpenDNS page of death appeared in my browser:


It says: If you experience this problem, we do not have any solution to this problem. We’ll fix this as soon as possible.

I say: How the heck are you going to fix it if you say you don’t have a solution??

Once again, I say goodbye to OpenDNS and hello normalized Internet!


  1. Hwew. Buti nga I chose Smart Bro 999 over PLDT MyDSL. OpenDNS solved my router glitch kasi eh. haha. good luck wit that issue po. 😀

  2. That message isn’t an OpenDNS message. That’s a message that the person who runs your network set up.

    Someone on your network is blocking Games sites — it has nothing to do with OpenDNS not being able to reach it. Maybe they are trying to make you think it’s us. 🙂

  3. I guess nahack ang PLDT. This is the second time na nangyari ito sa kanila.

    Tingin ko rin “custom error” ang cinonfigure kasi di naman siguro gagawa ng ALL-CAPS error ang OpenDNS.


  4. Andrew,

    The message you see in all caps is “custom block message” that we allow network administrators to input when they setup OpenDNS for their users. This is in no way a real OpenDNS error message.

    Since your ISPs logo also appears, if looks like they setup an OpenDNS account and set some very odd prefrences. Most ISPs do not block the “Games” category.

    We will look into this issue on our side, but please feel free to contact me directly at the address I put in for this comment.

  5. I agree w/ opendns that the problem is w/ ur provider. I don’t experience any problem w/ opendns, i experience problem more on PLDT and SmartBro. Maybe “they” want you to think that the problem was not from them. Diversion tactics. maybe 🙂

  6. well, i experienced that too… as mike said, your ip is pldt. maybe pldt made some configurations. to resolve my problem, just change my dns server to sprintlink… cheers!!! and now its better!

Leave a comment

Your email address will not be published. Required fields are marked *