NetNanny... Proxy servers...
etc. ============================================================== ASB - http://www.ultratech-llc.com/KB/?File=~MoreInfo.TXT ============================================================== -----Original Message----- From: Salvatore Palmisano [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 11, 2001 2:09 PM To: NT 2000 Discussions Subject: RE: Hosts File Usage We're not using them in production, Im researching the possibility of restricting web sites on a home machine from our nine-year-old. Every once in a while there will appear a site or two we'd rather him not visit, and after speaking to him about it I usually add the site to the hosts file (unbeknownst to him) like so: 0.0.0.0. bad.site.com ns.site.com ns1.site.com #...et cetera I can restrict him from viewing/editing/deleting the file with NTFS and it seems to be working. Anytime I try to browse a site Ive listed in the hosts file, MSIE returns a DNS error as expected. Id like the ability to block all instances of a site (*.site.com) instead of having to enumerate them all individually. Its a temporary fix, I know...but it'll work until he figures out how to start hacking the machine or covering his tracks <g> --Salvatore -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Flanagan, Kevin Sent: Thursday, October 11, 2001 1:43 PM To: NT 2000 Discussions Subject: RE: Hosts File Usage Hosts files are bad, use DNS. If you must use a hosts file, then remember it's just as the name says, hosts, not networks. Each server, or virtual server, needs to be individually listed. I have to ask, why are you using hosts files in this day and age? Kevin ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
