Error 403 on website, works well with Google DNS not with OpenDns

Comments

7 comments

  • Avatar
    rotblitz

    The reason may be content filtering. You ask OpenDNS to return a false IP address under certain circumstances.

    When visiting this site, the following domains are being queried:

    www.7daystodie.com
    7daystodie.com
    fonts.googleapis.com
    themes.googleusercontent.com
    s.ytimg.com

    If any of those domains are impacted by your content filtering settings, then the page may not load properly.

    Also, HTTP 403 means "forbidden", i.e. you attempt to access a URL you do not have the right to view or not with the method you're using. This is often returned when trying a directory listing where the webserver configuration has been set to not allow it, or if your user agent (browser) tries a GET instead of a READ.

    0
    Comment actions Permalink
  • Avatar
    deathsangel

    I do not have any content filtering, I disabled that long ago...

    I know the error 403, but I still do not understand why Google Public DNS does not cause me this issue. From what I checked it seems OpenDNS is trying to access a dead IP since a couple of days...

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    "I do not have any content filtering, I disabled that long ago..."

    So, you e.g. do no longer run an Updater? Then your IP address may be registered with another OpenDNS network and you do have content filtering without knowing it...

    "I still do not understand why Google Public DNS does not cause me this issue."

    All OpenDNS locations (http://www.opendns.com/support/cache/) return 192.163.251.135 for this domain, same as Google DNS. So it's hardly to believe that it is a DNS problem.

    "From what I checked it seems OpenDNS is trying to access a dead IP since a couple of days..."

    Sorry, I don't understand what this could mean. OpenDNS doesn't "access" IP addresses at all. DNS in general is the phone book of the internet, not the phone lines.

    0
    Comment actions Permalink
  • Avatar
    deathsangel

    1. My IP is updated and the filtering is set to "None"

     

    2. I know what a DNS is, I just wrongly express what I meant. When I switched OpenDNS to Google Public DNS the URL (7daystodie.com) was translated into another IP... different from the one that OpenDNS translate it into. I am trying to find where I noted the one I got from Google Public DNS.

    After contacting about 10 people who do not use OpenDNS they all told me they could access the website perfectly fine. Two of them switched their DNS to OpenDNS for a test and strangely they were unable to access that website anymore.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    I didn't succeed with reproducing your problem.

    "When I switched OpenDNS to Google Public DNS the URL (7daystodie.com) was translated into another IP... different from the one that OpenDNS translate it into."

    Exactly this is what I couldn't reveal. You can check yourself:

    nslookup www.7daystodie.com. 208.67.222.222               (OpenDNS result)
    nslookup www.7daystodie.com. 8.8.8.8                           (Google DNS result)

    For me every DNS service returns 192.163.251.135.

    0
    Comment actions Permalink
  • Avatar
    deathsangel

    I'll take screenshot to show you I am not crazy.

    0
    Comment actions Permalink
  • Avatar
    deathsangel

    Alright well... I dunno what happened but during my switch back to OpenDNS now the website loads normally... ...  wow. Maybe something to do with my local cache, even though I cleared it?

     

    Interesting. Well thanks Rotblitz, sorry for the bother?

    0
    Comment actions Permalink

Please sign in to leave a comment.