There was a thread similar to this last December.. I mentioned blocking sites at the router level.
http://www.daemonforums.org/showthread.php?t=2531
If you really want to do this locally, the hosts file was a valid option.. but antivirus software may revert such changes.
Are you sure you made the correct changes in
C:\Windows\system32\drivers\etc\hosts?
Quote:
Originally Posted by Windows NT/XP Hosts file
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 myspace.com
127.0.0.1 www.myspace.com
|
This does seem like a stopgap measure though, it doesn't cover all possible myspace.com subdomains..
Do you run your own local caching/forwarding DNS server? BIND has an interesting feature called "view", you could create a bogus myspace.com zone and have it only effect your Wife's activity.. presuming she has a static IP address.
/var/named/etc/named.conf:
Code:
view "spousal_trickery" {
match-clients { wifes_computer; };
recursion yes;
zone "myspace.com" {
type master;
file "master/myspace.com ";
};
};
/var/named/master/myspace.com:
Code:
@ IN SOA myspace.com. tooty.myspace.com. (
? ; serial
? ; refresh
? ; retry
? ; expiration
? ) ; minimum
NS localhost.
A 127.0.0.1
*.myspace.com. A 127.0.0.1
Just an idea, but probably a bad one.. my other solution was in that thread I linked above.