Seems like the instructions are somewhat flawed as simply stopping the DNSCache and DNSClient services is only good for that session, once you reboot they will be started again.
The DNSClient is the important one as if that isn’t running there will be no dnscache.
So this really is a one off measure to just access security sites whilst trying to remove conficker if you had it.
The DNS Client service is really only needed if the system is part of an corporation’s network using Active Directory and can really slow down browsing when using a large HOSTS file and thankfully HostsMan disables DNS Client service if it is installed to manage the HOSTS file. http://www.sturmnet.org/blog/2005/02/09/xp-dnsclient
I use OpenDNS as it has detection for known bad sites and prevents visiting there: http://www.opendns.com
I said important only in that of the two that is the one to stop as without it the other won’t work. I have my DNS Client set to Manual so it is available to those that require it (noting depends on it in my system).
I’m loath to disable services as that can really cause problems at least on manual it would be started if there was a dependency. I wouldn’t recommend either manual or Disabled in somewhere like the forums as you don’t know if there is something on their system that requires it, outside of conficker that is ;D
I agree with you that is more of a theoretical story than it is of practical value, but I passed the link as I found it, I hand it down, we share our views together in the thread and we are all so much the wiser.Well, this was the way I learned a lot on several issues here. So thanks for your reactions, ye all, learning about security is a mutual process,