ITsVISTA
Information that makes life easier when it comes to installing, managing, and using Windows Vista.
Start About FAQ Blogroll Shop
← KB932173 links for 2007-04-15 →

Vista's DNS Client Service

April 14th, 2007 · 8 Comments · 9,630 views
Tags:

ServicesThe DNS Client is not specifically required to use the internet. What it does do is try to improve your internet experience. The most basic way it does this is by caching domain name addresses, which speeds up the browsing experience. This service also determines if an IPv4 or IPv6 address would be more appropriate for a domain name. In an enterprise, it can also be useful in letting the network know your PC’s domain name, which can simplify finding shared resources. Though it is safe to disable this service, most users will likely end up with slower internet browsing, as well as other minor DNS related issues, so it’s best to leave this one on.

Display Name:
DNS Client
Service Name:
Dnscache
Process Name:
svchost.exe
Description:
The DNS Client service (dnscache) caches Domain Name System (DNS) names and registers the full computer name for this computer. If the service is stopped, DNS names will continue to be resolved. However, the results of DNS name queries will not be cached and the computer’s name will not be registered. If the service is disabled, any services that explicitly depend on it will fail to start.
Path to Executable:
%windir%\system32\svchost.exe -k NetworkService
Default Startup:
  • Home Basic: Automatic
  • Home Premium: Automatic
  • Business: Automatic
  • Enterprise: Automatic
  • Ultimate: Automatic
Log On As:
Network Service
Desktop Interaction:
No
Depends On:
None
Required For:
None
Memory:
N/A
CPU:
N/A
Do you know something about this service that I don't? Please leave a comment below so I, and everyone else reading this, can benefit from your knowledge!

Get notified of new posts for FREE via RSS or E-mail

Subscribe to ITsVISTA!

Digg Digg | Add to Mixx! Mixx | Netscape Propeller | Slashdot Slashdot | Stumble Stumble

Related Posts

Comments

  • Eric

    Apr 14, 2007 at 3:50 pm

    A large HOSTS file (over 135 kb) tends to slow down a computer. This only occurs in W2000/XP/Vista. Windows 98 and ME are not affected.

    To resolve this issue it is recommended you disable this service. If indeed you are using a HOSTS file.

  • Joe

    Apr 14, 2007 at 4:18 pm

    Thanks for the pointer Eric! I did a search on your info and found this at Wikipedia:

    “It also reads the entire hosts file into that cache as well, which can cause a slowdown at boot time if the file is large (most likely because it is being used for ad filtering). One solution is to disable this service. However, Microsoft claims that “The overall performance of the client computer decreases and the network traffic for DNS queries increases if the DNS resolver cache is deactivated.”

    This would support your point, but it sounds like ‘your mileage may vary’ depending on how big your HOSTS file is, how much browsing you do, etc.

  • Eric

    Apr 15, 2007 at 11:48 am

    Hey Joe, thanks for clearing that up. I never bothered to “Wiki” that, I was just always taught to to watch the size of your HOSTS file, and disable DNS if it got too big.

    Off topic a bit, I love the new site design!

  • Joe

    Apr 17, 2007 at 9:04 pm

    Thanks Eric, I’m trying hard!

  • T.

    May 31, 2007 at 12:27 am

    So then the summary/consensus so far is that a HOSTS file larger than 135K or whatever may slow your computer down momentarily (aka for a mini-second) when you logon.

  • david

    Jul 8, 2008 at 7:37 pm

    DNS Client also makes it’s own decisions about how to resolve requests. May choose to use Secondary DNS server instead of Primary DNS Server. May also use WINS or AD as data source instead of DNS query? May be required if alternative data source is required to find a required server. Should be turned off while debugging DNS problems.

    First reports were that Win2000 cache was much slower on every request with a large hosts file, because the entire hosts file was cached by the Win200o DNS Client. Without the Win2000 DNS client, only positive/negative hits from the hosts file were cached (and hosts lines marked for caching). This situation may have improved with modern computers and more recent versions of the client.

  • Hostsman a simple way to blocks ads and malware | JonnysBlog

    Apr 29, 2009 at 3:44 pm

    [...] cause the dns client to slow your computer down disabling is recommended although there seems to be pro’s and cons to doing so. This freeware app can also backup, find errors in and find hijacks in your hosts. [...]

  • Cristian

    Jun 16, 2009 at 11:15 pm

    i’ve got my hosts file in vista… i add an entry like 214.90.51.15 http://www.yahoo.com … supose that 214.90.51.15 is the ip for another page (not yahoo) that exists… when y go to cmd and put
    ping http://www.yahoo.com it says pinging to 214.90.51.15 but when go to firefox or explorer or chrome to get de page http://www.yahoo.com i get yahoo… and not the page on ip:214.90.51.15 the PC is with router uses wireless conection and the user is adminitrator and i flush de DNS cache and its continuos… why??? there is a modification in the form that it’s works?? because in XP dont do that and i go to see registry for de order of resolution and all was ok… please help sorry for my english :$

Leave a Comment

← KB932173 links for 2007-04-15 →