Your IP:

Our Forums Have Moved!

Visit our new forums at http://community.opendns.com/forums/ to post on topics and read the latest content. These forums are now read-only archives.

K-12 Forums

Talk with other K-12 network administrators in your state.

Or see all states.

Categories

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

This discussion has been inactive for longer than 30 days, and is thus closed.
    • CommentAuthorwazzaoz
    • CommentTimeJun 5th 2012 edited
     permalink
    I'm seeing a difference in the filtering of adult sites between FamilyShield and OpenDNS Basic. With FS, if I do a Google Image search on "sex" and then click one of the explicit images presented, the resulting page is blocked as expected. When I changed to Basic (because I wanted the more advanced control it offers) I set my filtering level to "High" and tested again, expecting the same sort of results as FS. However, the site loaded, despite being clearly explicit and being filtered by FamilyShield. The test URLs (www.internetbadguys.com etc) or browsing to well known sites (e.g. www.porn.com) indicate that OpenDNS is working, as they are blocked.

    Is it intentional that the behaviour of these two filtering methods is different?

    I prefer the filtering outcomes of FamilyShield, but I would like the control that Basic gives me. Is it possible that I can have my cake and eat it too?

    Please find below my config if this is of any interest here. FYI, I flushed the browser cache (FF10.0.1) prior to flushing the resolver cache.
    ----------------------------------------------------------------------------
    C:\>ipconfig /flushdns

    Windows IP Configuration

    Successfully flushed the DNS Resolver Cache.

    C:\>nslookup -type=txt debug.opendns.com.
    Server: ds9.warren-au.com
    Address: 192.168.111.3

    Non-authoritative answer:
    debug.opendns.com text =

    "server 5.sin"
    debug.opendns.com text =

    "flags 20 0 2f6 27f00f1189ef3"
    debug.opendns.com text =

    "id 8977007"
    debug.opendns.com text =

    "source 27.33.33.45:50001"

    C:\>nslookup www.exampleadultsite.com
    Server: ds9.warren-au.com
    Address: 192.168.111.3

    Non-authoritative answer:
    Name: www.exampleadultsite.com
    Address: 67.215.65.130
    ----------------------------------------------------------------------------

    Thank you.
    • CommentAuthorrotblitz
    • CommentTimeJun 5th 2012
     permalink
    Home Basic and FamilyShield are supposed to raise the same result in case you blocked the same categories in Basic as are blocked by default in FamilyShield.

    You had to investigate for particular domains where it seems to be different.
    • CommentAuthorwazzaoz
    • CommentTimeJun 5th 2012
     permalink
    OK... but I don't know what categories are blocked in FamilyShield. I think that in this case though that's unlikely the issue - this is clearly adult content, I'm not sure what other category it could possibly fall into. I've checked the Knowledge Base but can't find any documentation on how FamilyShield is configured under the covers.

    So I can test this further, can I find out exactly what categories FamilyShield blocks? That way I can set my category blocks the same way in Basic and see what happens.

    Cheers.
    • CommentAuthorrotblitz
    • CommentTimeJun 5th 2012
     permalink
    It was once documented, but isn't now anymore.
    http://web.archive.org/web/20110702235551/http://www.opendns.com/home/familyshield
    (Yeah, the internet doesn't forget anything. :cool:)
    Not sure if something has changed in between.
    Thankful People: wazzaoz
    • CommentAuthorwazzaoz
    • CommentTimeJun 6th 2012
     permalink
    Looks like things have sorted themselves out overnight... maybe some things take more than three minutes to propagate.

    Thanks for your help.
    • CommentAuthorrotblitz
    • CommentTimeJun 6th 2012
     permalink
    "maybe some things take more than three minutes to propagate."

    Certainly not if you orderly cleared your caches.

This discussion has been inactive for longer than 30 days, and is thus closed.