In your message regarding Re: OpenDNS and Spamassassin dated 02/04/2009, Evan Platt said ... >EP- At 02:52 PM 4/2/2009, you wrote: > >Personally I wouldn't use OpenDNS on a server (except maybe for > >squid). It's not a normal DNS server, it does things that are aimed at > >browsers like spelling correction, and redirecting failures to it's own > >web servers. The latter presumably breaks the NO_DNS_FOR_FROM test, > >and I wouldn't be surprised if other tests are affected too. >EP- Agreed. Bad idea. >EP- One of our corporate customers for some reason wanted an opendns >EP- server configured at their office, in addition to their dns servers. >EP- They called when people weren't able to VPN using a Non FQDN (which >EP- internally resolves on their dns - ie "eastcoast.home". >EP- I logged into our server, and saw the OpenDNS was resolving >EP- EVERYTHING - blah.blah , nothing.nothing, etc. >EP- Sorry, OpenDNS had to go.
Thanks for the rapid response. Can I send all my BIND questions here? ;-) Thanks to especially to "Yet Another Ninja" for pointing me in exactly the right direction. Noted the stuff about OpenDNS being "not a proper DNS" and, as I have squid set up but not in use, I may just point squid at it and go back to using my ISP's DNS servers as forwarders. Thanks again. -- Mike
