You might want to consider using opendns (<a href="http://opendns.com">http://opendns.com</a>)<br><br>and or Phishtank ( <a href="http://www.phishtank.com/">http://www.phishtank.com/</a> )<br><br>In combination with your DNS setup. This basically gets rid of a lot of the problems of phishing and is a bit more proactive about it than sitting back and waiting to be told.<br>
<br>I use opendns on all my networks now, and setup internal DNS's as caches against their servers. As a bonus you get some stats and other blocking options for free.<br><br>Kind regards<br><br>JoelW<br><br><div><span class="gmail_quote">On 10/02/2008, <b class="gmail_sendername">t94xr</b> <<a href="mailto:webmaster@t94xr.net.nz">webmaster@t94xr.net.nz</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Im a kiwibank customer and I knew about this ages ago, they mention it<br>on the login page to kiwibank<br>I reported his domain into his registrar for use of fishing<br><br>Cameron W<br>_______________________________________________<br>
adsl mailing list<br><a href="mailto:adsl@lists.unixathome.org">adsl@lists.unixathome.org</a><br><a href="http://lists.unixathome.org/mailman/listinfo/adsl">http://lists.unixathome.org/mailman/listinfo/adsl</a><br></blockquote>
</div><br>