This is the server forum. Are you using Snow Leopard Server 10.6 OS X Server? (I'm guessing that you are using the OS X client software and not using the server software, in the following answer...)
Please provide details of the "problems" you have experienced and the "workarounds" that you have implemented. URLs, errors, diagnostics and related details could be useful in resolving this.
For the particular DNSchanger botnet attack (and more) that was what was apparently discussed in that SFGate article (and in little technical detail), verify that your OS X and Windows clients are using your ISP DNS servers, or using Google DNS, or the DynDNS folks, or (as various of us utilitize) your own DNS servers, and then usually without forwarders. AFAIK, that was specifically targetting Microsoft Windows platforms, as well.
In general, DNS attacks are independent of browser. They redirect everything. The question is how the changes are made to DNS. That can be via various low-level means, or through an operating system vulnerability, or through software that the user has downloaded and installed; whether it's a tool that was intentionally loaded (and that contained malware), or a bogus video player or other tools, or some other means. DNSchangrer got access into Windows.
I don't think DNSchanger is relevent here. (And much of what I've read about malware in the mass press hasn't been particularly accurate, or particularly useful.)
As for the trigger of your particular issue, this could easily be (innocent) issues with your ISP DNS server(s), with your network connection, with your gateway, or something with the particular client systems. Details of what you are encountering would be useful in help troubleshooting this.
My first assumption would be a DNS error within the ISP DNS server(s). Those can be common, and sometimes quite pernicious. Try setting your DNS to the Google DNS servers (8.8.8.8 and 8.8.4.4) and see if your DNS stabilizes. Here's the (Applications > Utilities > Terminal.app) Terminal.app command that will flush your local DNS caches (on 10.6 and later), and reload from your (existing, or new) DNS server(s); invoke this after changing your DNS servers.
sudo killall -HUP mDNSResponder
This requires you to enter your Administrative password, but will not make changes to your configuration beyond flushing your local DNS caches.