Does not block images

Comments

3 comments

  • Avatar
    rotblitz (Edited )

    Correct, a DNS service cannot recognize images, just domain names. What you falsely call URL is a domain name. If you don’t want to see images, you’ll need to block the domains where the images are hosted on if not already blocked by your settings.

    Another non-OpenDNS solution is described here:
    https://support.opendns.com/hc/en-us/articles/227986807-How-to-Enforcing-Google-SafeSearch-YouTube-and-Bing

    0
    Comment actions Permalink
  • Avatar
    jasonfitt

    Thank you. My mistake, domain name, not URL. I'm not a tech person. Not sure how I feel about you using the word "falsely" here. What are you getting at? If you are a tech support, I'd expect a little more professionalism. 

    Also, how many thousands of domain names are there, and how many new ones are created every year? I don't know the answer, but me blocking every domain name manually doesn't seem like a feasible solution. The second solution with the link requires a more tech/internet savvy person than me. What a headache.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    I revoke the word “falsely” and replace it by “in error”.  I’m a user like you, so I do not need to be professional. I just say what and how I want to say it.

    Well, these thousands of domains do not host porn images. I bet you did find only a handful of domains where you could find porn images and which are still not blocked by your current settings. No problem to add these few domains to your blocklist.

    0
    Comment actions Permalink

Please sign in to leave a comment.