Warning: sem_get() [function.sem-get]: failed for key 0x152b: Permission denied in /home1/vmetccom/public_html/treesum/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 98
Protect your family online with OpenDNS | treesum.homeip.net
Search
Categories
Calendar
April 2008
S M T W T F S
« Mar   May »
 12345
6789101112
13141516171819
20212223242526
27282930  

Protect your family online with OpenDNS

OpenDNS is a free Dynamic Name Resolution Server (DNS) replacement service that has some very cool internet protection and web site filtering controls for your family. I’ve been using the DNS replacement service for several years now, but I have recently discovered the features that help make the home network more secure. I am pleasantly surprised and very impressed by the reporting, control, and the protection I now have from this completely free service.

From the OpenDNS web site:

“OpenDNS protects millions of people a day across hundreds of thousands of schools, businesses and homes. We block phishing sites, give you the power to filter out adult sites and proxies among more than 50 categories, and provide the precision to block individual domains.”

To start controlling your family’s internet usage you must open a free account. After that OpenDNS needs you to set up basic information about your home network so that you can enable content filtering and start monitoring. If you have a dynamic ip address and your ISP changes your external address frequently, you can use one of several free services like DynDns to automatically notify and update OpenDNS when your ip address is changed.

OpenDNS Features Summary and links:

Possibly Related

Tags: , , , , , , ,

blog comments powered by Disqus

Warning: sem_acquire(): supplied argument is not a valid SysV semaphore resource in /home1/vmetccom/public_html/treesum/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 107

Warning: sem_release(): supplied argument is not a valid SysV semaphore resource in /home1/vmetccom/public_html/treesum/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 116