|
|||||||||||
|
Re: blocking msn messenger
From: Nick Holland <nick(at)holland-consulting.net>
Date: Mon Jan 20 2003 - 21:01:15 EST
John Reuchlin wrote:
Not really a tech@ topic... Three ways I can think of...
The trick: MSN Instant Messenger doesn't hard-code IP addresses in the program (not certain of this, but a safe guess, I would think), they code in names. So, let's say it looks for "im1.msn.com" through "im48.msn.com". You set up your DNS resolver to redirect any queries for those names to your local policy-web server. Or...you say "screw it" and redirect all of msn.com to the local web server. Bingo, no more MSN-IM. (and if enough people start doing this, MSN might decide the loss in traffic on msn.com isn't worth letting people use MSN-IM over the objections of IT people. Nail aol.com for me, while you are at it. 8-) Follow it up with rules to insure that the only node which can reach other DNS servers is your internal DNS resolver, and you have pretty well locked them out of any site you have a problem with. Did this at a school, it has worked rather well. I set up a simple script to add new names: "block rotten.com" and everything on rotten.com is suddenly looking like the school's policy page. Nick. -- http://www.holland-consulting.netReceived on Tue Jan 21 03:32:59 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 13:48:28 EDT |
||||||||||
|
|||||||||||