Provide for Scheduled Blocking

Not planned

Comments

9 comments

  • Avatar
    rotblitz
    1. Duplicate of https://support.opendns.com/entries/21855380-Domain-blocking-at-certain-times-of-the-day-only
    2. As you can see from the other thread, this is not planned for "normal" OpenDNS, because...
    3. This solution exists: http://www.opendns.com/support/article/125
    0
    Comment actions Permalink
  • Avatar
    Chris Frost

    Scheduled filtering and per-user web content filtering for the home with OpenDNS are currently only available through the Netgear Live Parental Controls program that comes bundled with new Netgear routers.

    For more information regarding this networking solution, please see: http://countries.netgear.com/lpc

    0
    Comment actions Permalink
  • Avatar
    s_mol

    Buying a different router is not always an option.  We use a corporate router that is mandated by my employer.  On the kids' computer, I have manually forced the use of your DNS service, making the blocking applicable to that computer only.  The ability to schedule access to youtube, facebook, etc. is very desirable in that configuration, and can not use a branded router.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    ...but you may be able to put your own Netgear router behind the existing router.

    0
    Comment actions Permalink
  • Avatar
    s_mol

    Now that would cause quite a problem with the network shares, network printer, and network scanner, wouldn't it?  Double NATting is NEVER recommended.

    OpenDNS is a great service, and it makes sense as a service.  It shouldn't require hardware - then it becomes a feature, not a service

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    "Now that would cause quite a problem with the network shares, network printer, and network scanner, wouldn't it?"

    No, why should it?  You connect all devices to the inner Netgear router you want to have controlled by LPC and the others to the outer router.

    "Double NATting is NEVER recommended."

    This is not really true.  But you may be able to switch the outer router to bridged mode, then you get rid of double NAT.

    "OpenDNS is a great service, and it makes sense as a service.  It shouldn't require hardware - then it becomes a feature, not a service."

    Yes, OpenDNS is a service, as any other DNS service is.  There's not more a DNS service can do.  If you want features, you have to run parts of things locally, be it a router or be it locally running programs as is with Umbrella.

    0
    Comment actions Permalink
  • Avatar
    s_mol

    Bridging the first router - and double NATting - kills the corporate tunnel.

    Long and short of it - we're asking for a feature on the service.  Pointing at "hardware" isn't a solution, it's a workaround.  And workarounds never work for everyone's situation.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    You did notice that this feature request was officially marked as not planned by staff before already, did you?
    If not, see my first response above.  There's really nothing to add, except maybe...

    "Pointing at "hardware" isn't a solution, it's a workaround."

    As I mentioned already in the other thread, even if scheduling would be supported by OpenDNS Home Basic, you would have to have a tool or local process flushing your caches, else scheduling would not take effect at all, but would take most stuff out of the caches ignoring your settings and scheduling.  You'll call it a "workaround" then too and would come back to complain about this...

    That said, there is no technical solution from a DNS service perspective.  You always have to have or do something locally, be it via Netgear (or other) router or via software or via (meaningless) manual intervention (i.e. flushing the caches on every device).

    0
    Comment actions Permalink
  • Avatar
    s_mol


    Yes, I noticed this is listed as "not planned."  That doesn't mean we shouldn't keep asking for it!  If those of us who want it are noisy enough, it will change from "not planned" to "planned."  Every business lives and dies by the motto "give 'em what they want!"

    "you would have to have a tool or local process flushing your caches..."


    No, that's not true.  If it were, "waiting 3 minutes" wouldn't work when I am currently adding and deleting domain names from the web filtering list.  Fact is, this is a DNS service, so even if the TTL on the master DNS record is large, you don't have to say so.  You can give a TTL that is the smaller of two numbers: The actual TTL or the time remaining before the item should be removed because of the scheduled time.

    Would it always be effective in every situation?  Of course not.  Intelligent users can get around it.  But then they also could get around OpenDNS completely by simply changing the DNS server on the computer from "automatic" or manually entered OpenDNS numbers to other widely known DNS servers like 8.8.8.8.

     

    0
    Comment actions Permalink

Post is closed for comments.