How to: Enforcing Google SafeSearch, YouTube, and Bing

Follow

Comments

91 comments

  • Avatar
    gene3

    Any idea of how this can be done on a DD-WRT router? I thought maybe using DNSMasq but I set that up and it didn't appear to work. If anyone has successfully done that, please help with screenshots. Thanks.

  • Avatar
    gene3

    Ok, thanks. Adding this to "Additional DNSMasq Options" appears to have worked:

    address=/www.google.com/216.239.38.120

    I will add all of the other google domains too (www.google.de, www.google.ca, etc.). The only problem will be if/when the IP address of forecsafesearch.google.com changes.

  • Avatar
    doafr

    This is driving me crazy.  I am jumping through hoops to get this set up and every path leads to a dead end.

    Google's advice is unhelpful in the extreme "Set the DNS entry for www.google.com to be a CNAME for forcesafesearch.google.com."  where do I find this mythical DNS CNAME setting?

    I have a local dns with forwarding to opendns - synology DNS doesn't allow me to define cnames to external domain. I have no other vehicle to act as a DNS server.

    My apple airport extreme wi-fi router has a dns cache, and you'd think it would let me configure the CNAME there, but no.

    I have tried the proxy route - but I can't find how to force all wi-fi clients to use the proxy

    I can't override the localhost file for all the phones & iPads etc on my network.

    So, please, how am I supposed to do this so that all wi-fi clients are prevented from accessing unsafe google search?

     

  • Avatar
    rotblitz

    "where do I find this mythical DNS CNAME setting?"

    As almost - in the related user documentation (manuals, guides).

    "I have a local dns with forwarding to opendns - synology DNS doesn't allow me to define cnames to external domain."

    Doesn't it?  A simple web search for "Synology DNS" got me to a different insight!

    https://www.synology.com/en-global/knowledgebase/tutorials/584

    Make the Google domains private domains (for your network), and configure the CNAME as explained in that guide.

  • Avatar
    doafr

    Thanks for the update.  I had seen this but I didn't know I could override the google domain in this way, that isn't obvious from the instructions.  However, it still doesn't solve my problem because I need to apply it for every single google domain (.com, .co.uk, .fr, .de, .ie etc) which is impractical.   Furthermore I don't know what to enter for all the other details 

    I still maintain that it is ludicrous that I (a naive IT user) need to get into all this.  It is doubly ludicrous that I need to create a home DNS to make my existing so-called secure DNS work more securely, and I am expected to understand that this makes obvious sense.

     

  • Avatar
    mattwilson9090

    You may think it is ludicrous, but there is no other option available. It can only be done on a DNS server or proxy server that you control, or some sort of service that specifically offers that kind of functionality. It cannot be done by a recursive DNS service.

    A far easier method has been pointed out to you, namely use OpenDNS to block the Search Engine category, and then whitelist whichever search engine provides the degree of censorship you are looking for. It also has the benefit of blocking all other search engines that return content that you find objectionable.

  • Avatar
    rotblitz

    "I need to apply it for every single google domain (.com, .co.uk, .fr, .de, .ie etc) which is impractical"

    ...but possible.  Complain with Synology if you're unhappy with what they offer.

  • Avatar
    grantsmith

    I'm using OpenDNS.  How do I create a CNAME record for www.google.com.  I'm surprised no one's asked this.  I can see where to do it in my router, but I'm bypassing my router for DNS so I can use OpenDNS.  I could put an entry in the HOSTS file on my Windows computers, but that doesn't help me with my problem device: an iPod touch.  I would have to jailbreak the device and I doubt the owner would go along with it.

  • Avatar
    grantsmith

    I found a work-around for my situation.  After digging in my router, I found my router itself was getting DNS settings from DHCP.  I changed it to use static DNS servers, pointed to OpenDNS.  For the DNS settings the router hands out to clients, I switched it from OpenDNS to the address of the router (I had to cheat and put the same address in both boxes, since it insisted on have two DNS servers).

  • Avatar
    mattwilson9090

    Many people have demanded (not asked) for some variation of creating a CNAME via OpenDNS, or for OpenDNS to do it for them. It has been the subject of many threads here, and many back and forth posts. The response has always been something that amounts to "OpenDNS is a recursive DNS service, not an authoritative DNS service, and only an authoritative DNS can do this. You can however do it on a DNS server of your own that you control". There have been many posts containing instructions or links on exactly how to do this for ones self. It's even discussed in this thread you posted to.

    What you did is one way to configure you the router, and it would allow you to use your router (probably using DNSMasq to provide your own CNAME for google). I prefer not to do that unless I have a specific need because many consumer routers are just too underpowered to handle DNS services without slowing down all internet traffic

  • Avatar
    utognazzi

    Hi, I create this batch file (only for windows user) that adds to all google domains the string 216.239.38.120

    This is a very simple batch file, I'm not a programmer. If you have some ideas to improve it, or if you find some issues, please share into this forum.

    I try it on my pc and it works. Please try it and tell me if it works...

    To run the batch file right click on the batch file and "Run as administrator"

    This is the code:

    @echo off
    findstr "216.239.38.120 www.google.com" C:\Windows\System32\drivers\etc\hosts
    if %errorlevel%==0 (
    goto end
    )
    @echo #forcesafesearch>> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com>> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ad >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ae >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.af >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.ag >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.ai >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.al >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.am >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.ao >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.ar >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.as >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.at >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.au >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.az >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ba >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.bd >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.be >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.bf >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.bg >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.bh >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.bi >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.bj >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.bn >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.bo >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.br >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.bs >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.bt >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.bw >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.by >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.bz >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ca >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.cd >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.cf >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.cg >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ch >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ci >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.ck >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.cl >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.cm >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.cn >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.co >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.cr >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.cu >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.cv >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.cy >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.cz >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.de >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.dj >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.dk >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.dm >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.do >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.dz >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.ec >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ee >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.eg >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.es >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.et >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.fi >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.fj >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.fm >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.fr >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ga >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ge >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.gg >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.gh >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.gi >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.gl >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.gm >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.gp >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.gr >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.gt >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.gy >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.hk >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.hn >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.hr >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ht >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.hu >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.id >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ie >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.il >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.im >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.in >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.iq >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.is >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.it >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.je >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.jm >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.jo >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.jp >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.ke >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.kh >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ki >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.kg >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.kr >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.kw >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.kz >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.la >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.lb >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.li >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.lk >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.ls >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.lt >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.lu >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.lv >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.ly >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.ma >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.md >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.me >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.mg >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.mk >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ml >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.mm >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.mn >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ms >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.mt >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.mu >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.mv >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.mw >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.mx >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.my >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.mz >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.na >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.nf >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.ng >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.ni >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ne >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.nl >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.no >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.np >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.nr >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.nu >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.nz >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.om >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.pa >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.pe >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.pg >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.ph >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.pk >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.pl >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.pn >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.pr >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ps >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.pt >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.py >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.qa >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ro >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ru >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.rw >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.sa >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.sb >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.sc >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.se >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.sg >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.sh >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.si >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.sk >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.sl >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.sn >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.so >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.sm >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.sr >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.st >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.sv >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.td >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.tg >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.th >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.tj >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.tk >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.tl >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.tm >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.tn >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.to >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.tr >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.tt >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.tw >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.tz >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.ua >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.ug >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.uk >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.uy >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.uz >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.vc >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.ve >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.vg >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.vi >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.com.vn >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.vu >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.ws >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.rs >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.za >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.zm >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.co.zw >> C:\Windows\System32\drivers\etc\hosts
    @echo 216.239.38.120 www.google.cat>> C:\Windows\System32\drivers\etc\hosts
    @echo #end of forcesafesearch>> C:\Windows\System32\drivers\etc\hosts

     




    safesearch_hosts.zip
  • Avatar
    utognazzi

    Hi, I create this batch file (only for windows user) that adds to all google domains the string 216.239.38.120

    This is a very simple batch file, I'm not a programmer. If you have some ideas to improve it, or if you find some issues, please share into this forum.

    I try it on my pc and it works. Please try it and tell me if it works...

    To run the batch file right click on the batch file and "Run as administrator"

  • Avatar
    utognazzi

    This is the file sorry




    safesearch_hosts.zip
  • Avatar
    utognazzi

    "unzipped"




    safesearch_hosts.bat
  • Avatar
    magdiel1975

    @gene3

    I use Tomato by Shibby firmware on my E2000 router and this works great, thank you..

    I have added this to the Dnsamsq setting..

    address=/www.google.com/216.239.38.120
    address=/www.google.co.uk/216.239.38.120
    address=/www.wwwlgoogle.ca/216.239.38.120
    address=/www.google.fr/216.239.38.120
    address=/www.google.it/216.239.38.120
    address=/www.google.es/216.239.38.120
    address=/www.google.nl/216.239.38.120

    but, is there a way to block this if the users search using bing or any other search engine?

    It doesn't seem to work if using any other search engine, and it's obvious why.. just wanted to know if there's a way to do this without having to set up a dns server.

  • Avatar
    magdiel1975

    Oh.. I added

    address=/www.bing.com/216.239.38.120 and it forces the user to use google.com as it redirects them to google.. hmm.. interesting... I guess this is a simple way around it.. haha.

  • Avatar
    rotblitz

    Because you redirect Bing to a Google IP address, you will indeed get a response from Google (with SafeSearch), not from Bing.  This is normal and not surprising.

    If you still want to use Bing, this is relatively easy.  You simply add explicit.bing.net to your "always block" list unless you already have blocked one of the Adult Themes, Nudity, Pornography categories.  Bing host such content under this specific domain.
    http://arstechnica.com/information-technology/2009/06/bing-moves-all-adult-content-to-explicitbingnet/

    Other search engines may have related but different specific tools to filter content.

  • Avatar
    magdiel1975

    cool.. I will try that.. but, I use Family Shield, so I don't have the option to block specific domains right?

    why do I need the automatic IP updater when using 208.67.222.222 - 208.67.220.220 - but not if I use 208.67.222.123 - 208.67.220.123?

  • Avatar
    rotblitz

    If you use the FamilyShield addresses, then explicit.bing.net is already blocked anyway.

    You can use also the dashboard (and an updater) with the FamilyShield addresses for other categories and single domains not covered by FamilyShield alone.  However, you cannot whitelist domains which are blocked by FamilyShield.

    You need the updater when you use the dashboard to keep your IP address information updated at OpenDNS, so that OpenDNS can associate your DNS lookups with your individual settings.

  • Avatar
    magdiel1975

    oh ok.. 

    I am using Family Shield, but I am able to pull nude pics in bing image searches, even if I have explicit.bing.net 
    even if I add it to the blocked sites in my router... images.search.yahoo.com works great.. it blocks all images from yahoo which means users will have to use another search engine.. what I am looking for is to be able to block ANY image search on the most common search engines and redirect them to google... I have not been able to find this for bing yet.. I have tried blocking www.bing.com/images, but it still pulls the images. - I have also cleared cache/cookies and flushed dns in CMD..but nothing seems to do the trick yet.

  • Avatar
    rotblitz

    I see.  It seems Bing has started to embed images as data within the web page, same as Google before.  These images are then no longer hosted on explicit.bing.net, but on e.g. www.bing.com.  Therefore they also have a Safe Search feature which you can use in addition.

    You cannot do this with OpenDNS alone, because a DNS service can block on domain name basis only, not based on keywords, images, web pages or any other objects.  Regarding www.bing.com, you can block it as a whole or not at all.

    "what I am looking for is to be able to block ANY image search on the most common search engines and redirect them to google"

    This is what you described above:

    "Oh.. I added address=/www.bing.com/216.239.38.120 and it forces the user to use google.com as it redirects them to google"

  • Avatar
    mattwilson9090

    All of these solutions hinge on the idea of identifying every possible search engine out there, all of the domains they use, and keeping those lists updated, especially as new search engines are created, or as existing ones add new domains. Adding it at the router level via DNSMasq or a DNS server is going to be more effective than modifying hosts files that may not be available on all devices, but it still requires a lot of ongoing effort.

    Why not just block the search engine category, and whitelist the domains for only those search engines you want to allow? This could be supplemented with the method for forcing Google's safeseach, or the other methods that other search engines have available to them.

  • Avatar
    magdiel1975

    This is exacty what I am trying to do.. but for example, I haven't found the way to just block the searc engine for bing... it's either all or nothing. - Can you tell me or point me in the right direction? - My wife likes bing for somethings, so I would rather just block the searc feature without blocking the entire domain.

    thanks.

  • Avatar
    magdiel1975

    OH.. I got what you're saying..

    Thing is I use Family Shield which does not have the option of whitelist... 

    **the should have an "Edit" otion for these posts...

  • Avatar
    mattwilson9090

    If you want to stay with Family Shield then you would need to set up a dashboard account and start blacklisting those domains you don't. If you want to use a search engine but only block some of it's content you'll need to research to see if a specific engine has something like Google's safesearch and figure out how to apply it for your entire network. I suspect that for most search engines there really isn't a way to do that. Since it appears that even blocking explcit.bing.net allows through traffic you don't want you'll have to check with bing to see if there are any other options, or just block bing entirely.

    Of course if you are going to the extent of adding additional blacklist items to FamilyShield you should consider using regular OpenDNS Home where you also have the option to whitelist domains. That way you could block the search engine category and then whitelist only google or whatever search engine you want to allow.

  • Avatar
    magdiel1975

    I am now back to using the OpenDNS home and have blocked Search Engines, but www.bing.com is still pulling up for me.. well, what I mean is that, image searches show up as blanks, but if I hover the mouse over them or click on the empty block, then the picture becomes visible.

  • Avatar
    mattwilson9090

    What do you mean that www.bing.com is still pulling up for you?

    I just checked and bing.com is classified in the search engine category. Unless you have whitelisted something, www.bing.com and all other subdomains of bing.com will be blocked.

    When you hover your mouse over those blanks or blocks are you reading the URL that they point to? I just doubechecked on bing, and all of the search results, and pictures associated with them, point somewhere else, such as espn.com or huffingtonpost.com. If you don't have those domains or categories they belong to blocked there is nothing that OpenDNS can do about it since that is content that does not require a DNS lookup just to display a link.

    Again, if you want to use a specific search engine, you are stuck with whatever content that search engine provides. If it provides links then those links are going to appear since that is content and OpenDNS does not filter content. The only way it will filter is if you click on a link, and the domain it leads to is blocked via your OpenDNS setttings.

    If you don't like the results that bing or any other search engine provides then you need to make sure it is blocked either by individual blacklisting or blocking the search engine category. Some search engines provide functionality similar to Google's safesearch, but you'll need to research it for that particular search engine, and it's highly unlikely that you'll be able to take advantage of them via OpenDNS since those mechanisms are likely to work in a way that a recursive DNS provider can address.

  • Avatar
    magdiel1975

    In my custom settings I have checked.. Adware,Proxy/Anonymizer, Nudity, Pornography and Search Engines..

    then on the Never block:

    chrome-signin
    google.com
    mail.google.com
    snapchat.com
    www.aol.com
    www.bing.com
    www.google.com
    www.snapchat.com
    www.yahoo.com
    www.youtube.com
    youtube.com

    as you can see.. I have whitelisted www.bing.com, so nude pics can be seen in image searches.. another issue I am having is with Youtube.. it won't open properly for me even though I also have it in the whitelist.. I have cleared the cache and flushed dns in CMD...but youtube won't open. - I wonder why is Youtue being filtered when it should be a "Social Networking" category which I am not blocking at all.

  • Avatar
    mattwilson9090

    That is to be expected with bing since that is the content returned when you do a search on there. If blacklisting explicit.bing.net doesn't do it you'll need to do some research on bing itself to see what functionality they have that is comparable to Google's safesearch. There is nothing else that OpenDNS can do for you since you have whitelisted it.

    As for Youtube, there have been multiple threads on here with people having problems with youtube. The problem is, to display videos youtube uses a lot of different domains, some of which aren't obvious and probably at least one of them is in a category you have blocked.. You should search for those specific threads and follow the advice in them. I watch youtube on a semi-regular basis and have the Adware and Proxy/Anonymizer categories in common with you, so it's not any of those categories that are you blocking you. Something in your blacklist could also be interfering with youtube.

    For future reference, since you have google.com, youtube.com and snapchat.com in your whitelist, there is no need to add any of their subdomains, such as mail.google.com, www.google.com, www.youtube.com and www.snapchat.comsince the main domain already covers the subdomains. If nothing else it will shorten your whitelist and make it easier to manage.

    Also, chrome-signin probably isn't a valid domain, so probably isn't doing anything for you.

Please sign in to leave a comment.