OpenDNS is an effort that aims to help users avoid phising attempts. It is a free to use service and extremely helpful for the home user. It is very easy to use. If you know how to configure your settings, you simply use the following two DNS servers (instead of the normal ones that your ISP tells you to use):

208.67.222.222
208.67.220.220

Alternatively you can go to their “Get Started“ page and continue from there. But what if you want to offer OpenDNS as a service for your users? Their FAQ has a simple answer: You can use the forwarders option in the named.conf^* of your DNS servers:

options {
:
  forward first;
  forwarders {
    208.67.222.222;
    208.67.222.220;
  };
:
};

This is fine if you want to switch everybody to use OpenDNS. However if you want to offer the service as an alternative for your users, you need to have a separate instanse of named running (maybe on a different machine), because simply using the above forwarding technique will result in having your cache server ask OpenDNS‘ servers even for your own domains. To avoid this traffic, you must include in its named.conf a forwarding⁺ clause for each of your local domains.

OpenDNS is not a panacea, nor a DNS replacement. IMHO, it is an excellent tool to use when web browsing. Should you decide to implement it, it is best that you offer it to your users via a (separate) caching server. But at the same time it is vital that you remember that there are valid reasons not to use it. However, as Paul Vixie writes:

“that having been said, if typosquatting is going to be done, opendns is the best way to do it among the ways i’ve seen. kudos to davidu and his team for the quality of their implementation and the openness of their launch.”

Further reading: Wikipedia article on OpenDNS.

[*] – I have a strong preference for BIND. However if you study the OpenDNS FAQ you will see that it works well with other DNS software too.
[+] – Some may opt to keep secondaries instead of forwarding.