Comments

2 comments

  • Avatar
    mattwilson9090

    The concept is a good one, but potentially fraught with difficulties on a service such as OpenDNS. Perhaps you could elaborate a bit more.

    The first thing is how do you want a DNS service to identify these scripts? Since DNS only knows about domain names it cannot identify things such as web pages, URL's, or content. IT would have no way to tell an embedded or third party script apart from any other content on a particular page or site. In order to block something you have to have a reliable way to identify it, and I off the top of my head can't think of a way to do that within the constraints of a DNS based system.

    Also, how would you want this option to be handled in the configuration options for an OpenDNS account? Would it be via an additional category, or some other mechanism?

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    As mattwilson9090 said, a DNS service like OpenDNS has no way to identify the "third party" or the "script" facts, because the context of "parties" and object types like "scripts" is not part of DNS, just of HTTP where a DNS service has no access to.

    A good example of a locally working tracker blocker is Ghostery's browser extension: https://www.ghostery.com/our-solutions/ghostery-browser-extention/
    OpenDNS could build a category with the related domains typically hosting the 3rd party trackers, so that OpenDNS users are able to block those.  The downside of such a category is that many web pages would be broken though, and a DNS service would not be able to handle this with the same granularity as Ghostery does.  For example, my avatar on the left side would not appear at all, because it is hosted on such a tracker domain normally blocked by Ghostery, but I have whitelisted it for me.

    0
    Comment actions Permalink

Please sign in to leave a comment.