Sun May 03, 2009 9:12 pm
There are some basic methods and some advanced...
If you are running proxy, and forcing http: thru it, then just add it to the access list with an action of deny.
I use the following methods...
1) Force all http traffoc thru a proxy.
2) Force DNS lookups to the DNS proxy.
3) Use OpenDNS forname resolution, and specify youtube as "banned".
4) Place a redirrect rule in the proxy settings to something like "get a life.com" (*.youtube.*)
This will block youtube by name but not by IP...
I would like to use address lists here, but havent had the time to figure it out yet..
IE a script or import routine that mailtained an address list for "banned" sites and then add a single entry to the proxy to look for items "on the list" and take action..
A "reverse" dns lookup would be handy...
IE: look at the URL, deturman that an address in contained, then look the addredd up and obtain the domain, if one is found, check it against the access list.. if not on a banned list, allow it, if banned then drop or re-dirrect..
For 80% , the baisic steps above will take care of the issue...
If the re-dirrect page states that youtube is not allowed, or that its use is controlled, then you can allways look at activity after the fact and address it with the user...
Some places frown on "blocking" access to sites.... but I dont belive there is a rule that says thay tou cant make it PAINFULLY slow.... that makes it "accessable" but un useable...
just an idea..