steveLaMi
asked on
Using hosts file to stop myspace usage
All our users are thin client users.
We do not have any web filtering so I would like to stop them from using myspace by the hosts file
I did a whois for www.myspace.com and it comes up with 63.135.80.46.
So I tried to build the hosts file to say
127.0.0.1 63.135.80.46
I thought by doing this it would send myspace requests to the localhost which is a dead page.
However, it is not working. What did I do wrong???
We do not have any web filtering so I would like to stop them from using myspace by the hosts file
I did a whois for www.myspace.com and it comes up with 63.135.80.46.
So I tried to build the hosts file to say
127.0.0.1 63.135.80.46
I thought by doing this it would send myspace requests to the localhost which is a dead page.
However, it is not working. What did I do wrong???
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
your entry should be
127.0.0.1 localhost
63.135.80.46 http://www.myspace.com
You have to flush the DNS cache before it will use the host file. Open run and type ipconfig /flushdns.
Alternately there is a great free service that can provide content filtering service site wide. The address is
http://opendns.org
Hope this Helps,
Sean
127.0.0.1 localhost
63.135.80.46 http://www.myspace.com
You have to flush the DNS cache before it will use the host file. Open run and type ipconfig /flushdns.
Alternately there is a great free service that can provide content filtering service site wide. The address is
http://opendns.org
Hope this Helps,
Sean
Putting the entry in LMHOSTS is pointless - that for Windows name resolution on the local network. And overcld9's post is incorrect. While you SHOULD have an entry for localhost, you would NOT have http:// in it AND, keep in mind - the idea is to BLOCK access to MySpace - a corrected entry (without http://) would actually guarantee access if DNS failed.
Sorry I gave you the wrong entry for my space .. you would want to change the ip addess for myspace.com .. I wouldn't use 127.0.0.1 as there are a number of apps that use the localhost designation.
for myspace
127.0.0.1 localhost
199.181.132.250 myspace.com
btw .. 199.181.132.250 is disney.com
for myspace
127.0.0.1 localhost
199.181.132.250 myspace.com
btw .. 199.181.132.250 is disney.com
funny I was fixing the post before I noticed any one else was commenting ...
An easy solution would be setting up an open source (aka free) Untangle application server between your router and your internal network in transparent bridge mode. The Untangle appliance has a Web Content Control module that blocks user access to specific Internet websites. The Web Content Control also enables you to choose among these categories to define web content control policies in your workplace. can can use custom URL blocklists for hosts, domains, and file types to block additional content.
Untangle Site:
http://www.untangle.com/
Untangle Product Overview:
http://www.untangle.com/index.php?option=com_content&task=view&id=86&Itemid=179
Untangle Demo/Video Overview
http://www.untangle.com/video_overview/
Untangle Quick Start Guide
http://www.untangle.com/pdf/Download_QuickStart.pdf
Untangle Server as a Bridge
http://wiki.untangle.com/index.php/Introduction#Untangle_Server_as_a_Bridge
Untangle Site:
http://www.untangle.com/
Untangle Product Overview:
http://www.untangle.com/index.php?option=com_content&task=view&id=86&Itemid=179
Untangle Demo/Video Overview
http://www.untangle.com/video_overview/
Untangle Quick Start Guide
http://www.untangle.com/pdf/Download_QuickStart.pdf
Untangle Server as a Bridge
http://wiki.untangle.com/index.php/Introduction#Untangle_Server_as_a_Bridge
Actually, if you're trying to redirect, I to another page, I would suggest creating a web page on your intranet that explains the acceptable use policy for your internet connection... then redirect your users to THAT page.
127.0.0.1 myspace.com
This should redirect all subdomains myspace might have outside of www.myspace.com. I would also put the entry in the lmhosts file as well for good measure.