Xhamster popular porn site working (not blocked)

Comments

20 comments

  • Avatar
    rotblitz

    Do you have IPv6 enabled?  Disable it!  Content filtering doesn't work with IPv6 yet unless you configured the IPv6 equivalents of the OpenDNS FamilyShield addresses.

    If it is not this, post the complete plain text output of the following diagnostic commands:

       nslookup -type=txt debug.opendns.com.

       nslookup xhamster.com.

    0
    Comment actions Permalink
  • Avatar
    waleed1999
    I use ipv4 nanostation m5 and what do u mean by this text and how to post and show u what u want exactly ?
    0
    Comment actions Permalink
  • Avatar
    rotblitz

    You open a command prompt window on your computer and enter (or copy & paste) the commands above.  Then you copy & paste the complete plain text output of the commands.

    0
    Comment actions Permalink
  • Avatar
    waleed1999

    is this good enough ?




    Capture1.PNG
    Capture2.PNG
    0
    Comment actions Permalink
  • Avatar
    rotblitz

    I said "plain text", not screen shot.  Regardless, your IP address 91.106.48.172 does not seem to be registered at https://dashboard.opendns.com/settings/
    Therefore your dashboard settings cannot take effect, because OpenDNS cannot associate your DNS lookups with your account.

    "All is blocked expect this popular website"

    This "all is blocked" is not possible.  This "blocking" must come from something else, not from OpenDNS, unless you have the FamilyShield addresses configured.

    0
    Comment actions Permalink
  • Avatar
    waleed1999

    i have and done FamilyShield addresses configured every adult site is blocked except this xhaster so what to do?

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Well, looking again deeper into your outputs, OpenDNS returns 146.112.61.106 (hit-adult.opendns.com) for xhamster.com, so this should be blocked by category.  If it isn't then these possible scenarios come to mind:

    • You have IPv6 connectivity enabled, and DNS lookup for xhamster.com is done via IPv6, not via IPv4 FamilyShield addresses or their IPv6 equivalents.  Especially, unlike many other sites xhamster.com can be reached also via IPv6.  As I said, content filtering doesn't work with IPv6 yet.  Again, disable IPv6 connectivity on the router or on the computer!
      https://support.opendns.com/entries/54333874
    • There is an entry for xhamster.com in your local hosts file which would circumvent OpenDNS.  Purge this entry from your local hosts file!
    • Your ISP uses web caching techniques.  This almost disregards your DNS lookup results.  In this case you must call your ISP to opt out from web caching, if possible at all.

    If you are still having troubles, run the diagnostics as of https://support.opendns.com/entries/21841580 and open a support ticket with OpenDNS.  You also open a support ticket if your IP address 91.106.48.172 is registered at your dashboard network.  I'm afraid the forum community cannot help any further then.

    0
    Comment actions Permalink
  • Avatar
    waleed1999
    U do not understand me ? Iam telling ur family shiled work on all sites except this xhamster this mean there is a bug in the dns server that the site gave us to prevent Abdult site from opening not from me the problem
    0
    Comment actions Permalink
  • Avatar
    rotblitz

    It seems we really don't understand each other.  Clarifying from my side:

    Firstly, re "ur family shiled", I'm a user like you and do not own or operate a FamilyShield. And secondly, you have demonstrated that OpenDNS' FamilyShield DNS resolver addresses return the correct and expected result for xhamster.com: 146.112.61.106 (hit-adult.opendns.com).  So, there's absolutely no bug, nothing to fix, or anything else wrong at OpenDNS.

    I just read all again what you wrote and found: "I use ipv4 nanostation m5"
    I didn't take too much attention of this before, because you said everything is blocked by OpenDNS except xhamster.com.  But now I have to come back to this:

    This device seems to be a wireless receiver and router.  https://dl.ubnt.com/guides/airOS/airOS_UG.pdf

    • Did you configure the OpenDNS FamilyShield addresses 208.67.222.123 and 208.67.220.123 in the DHCP Client section on this device?
    • Did you disable the "DNS Proxy" on this device and replaced it by the OpenDNS FamilyShield addresses?
    • Did you disable IPv6 on this device?
    • Can you confirm that connected devices are actually using OpenDNS?  http://welcome.opendns.com/
    • The PC where you executed the diagnostic commands, is it connected to this device?

    If you say "yes" to all, then follow the instructions I have given before, else rectify the items where your answer is "no".

    Btw, while checking your device's manual, you can use it also to keep the OpenDNS dashboard updated with your IP address via DNS-O-Matic.

    0
    Comment actions Permalink
  • Avatar
    waleed1999
    Ok this does not prove iam using ipv4 and family shield of open dns?


    image.png
    image.png
    0
    Comment actions Permalink
  • Avatar
    mattwilson9090

    The screenshots indicate that the first and third bullet points in rotblitz last reply have been confirmed. It doesn't indicate anything definitive about the 2nd bullet point, namely if "DNS Proxy" is disabled.

    You still need to address the 4th and 5th bullet points. All of the things he asked for in his last post are necessary to get the information needed to assess your situation and what is going on. Without it, it's pretty much impossible for him or anyone else to help you.

    0
    Comment actions Permalink
  • Avatar
    waleed1999
    @mattwilson9090 what's do u mean. ?
    0
    Comment actions Permalink
  • Avatar
    mattwilson9090

    It means you are not providing the information that is need in order for you to be helped. You need to answer all of the points that rotblitz raised, not just some of them.

    0
    Comment actions Permalink
  • Avatar
    waleed1999
    Well all of the point I can answer by yes
    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Great, then xhamster.com is being blocked by OpenDNS for you, as you have demonstrated.  If you can access it nevertheless, you or your ISP are circumventing OpenDNS on your network, on your computer or on your browser.  The problem is unrelated to OpenDNS.  OpenDNS has done its jobs as far as it should and could.  It returns its own IP address instead of xhamster.com's IP address.  This is all OpenDNS as a recursive DNS service can do.

    0
    Comment actions Permalink
  • Avatar
    waleed1999
    But why then any another adult sites open dns do good job and blocking it except xhamster?
    0
    Comment actions Permalink
  • Avatar
    mattwilson9090

    According to the information you grudgingly provided OpenDNS is returning the expected results for this domain name. As rotblitz stated this has nothing to do with OpenDNS, but rather you or your ISP are doing something to prevent OpenDNS to prevent working properly.

    You've stated that other websites are being blocked. Are you receiving an actual OpenDNS message that they are blocked, or something else? In other words, how do you know that OpenDNS is actually blocking these websites and not something else?

    0
    Comment actions Permalink
  • Avatar
    waleed1999
    I can. Know because this popup


    image.png
    0
    Comment actions Permalink
  • Avatar
    rotblitz

    "But why then any another adult sites open dns do good job and blocking it except xhamster?"

    How can we other users know?  It's your equipment circumventing OpenDNS for xhamster.com, not ours.  You should know best what your stuff does, and we can guess only.

    My suggestion to follow up with this is to run this Diagnostic Tool, entering xhamster.com as the domain to test, and then you open a support ticket with OpenDNS including the link to your diagnostic results and a link to this thread.  The diagnostic results can be viewed only by you and OpenDNS staff.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    "But why then any another adult sites open dns do good job and blocking it except xhamster?"

    How can we other users know?  It's your equipment circumventing OpenDNS for xhamster.com, not ours.  You should know best what your stuff does, and we can guess only.

    My suggestion to follow up with this is to run this Diagnostic Tool, entering xhamster.com as the domain to test.
    https://support.opendns.com/entries/21841580

    Then you open a support ticket with OpenDNS (tab "submit a request" above) including the link to your diagnostic results and a link to this thread.  The diagnostic results can be viewed only by you and OpenDNS staff.

    0
    Comment actions Permalink

Please sign in to leave a comment.