On 2-Apr-2009, at 15:56, Evan Platt wrote:
I logged into our server, and saw the OpenDNS was resolving
EVERYTHING - blah.blah , nothing.nothing, etc.
This is not a OpenDNS problem, this is a problem with the know-nothing
who set it up for their system. I used OpenDNS for quite a while on
my mailserver (several months) and had no such issue.
Configure it right, and it works quite well, and it is VERY
configurable.
Sorry, OpenDNS had to go.
Or, you know, configured correctly.
Each of these is a configuration option:
Allow users to create child networks
Enable stats and logs
Enable typo correction
Exceptions for VPN users
Enable filtering of .cm wildcard
Block internal IP addresses
Apply my shortcuts to this network
Makes all your shortcuts work on this network, whether you're signed
in or not.
Enable OpenDNS proxy
Routes certain address bar requests through a simple proxy, ensuring
that your shortcuts and other OpenDNS features always work. For more
details, including potential privacy issues you should be aware of,
read our KB article.
Enable Botnet protection on this network
Blocks infected computers on your network from connecting to botnet
central controllers. At this time, this feature blocks the Conficker
virus, and will be expanded to include others.
--
You and me
Sunday driving
Not arriving
