From: Jonathan de Boyne Pollard on 27 Mar 2010 17:36 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <p>Why not research your problem before posting, instead of posting revised messages every ten minutes?</p> <blockquote cite="mid:hol99n$iuo$1(a)tioat.net" type="cite"> <p>I just remembered WHY I set the DNS Client service to Manual. I have a huge hosts file (with spam blocking). I don't remember the problem but that is why I disabled the DNS Client service.</p> <p>So my question has morphed to ... </p> <p>What does the DNS Client service actually do (besides slowing down huge hosts files and prevening network repairs)?</p> </blockquote> <p>Actually, the DNS Client speeds up things when one has huge hosts files. Without the DNS Client service, the hosts file is read and processed by every individual application process for every individual query. With the DNS Client service, the hosts file is read and processed once, by the DNS Client service at startup, and then re-read whenever the DNS Client service sees that it has changed.</p> </body> </html>
From: Jonathan de Boyne Pollard on 28 Mar 2010 04:35 > > > Since it appears no one has answered your question....I will. > One person had: the person who asked the question, some 15 minutes after asking it.
From: DanS on 28 Mar 2010 10:14 Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups(a)NTLWorld.COM> wrote in news:IU.D20100328.T083553.P504.Q0(a)J.de.Boyne.Pollard.localhost : >> >> >> Since it appears no one has answered your question....I >> will. >> > One person had: the person who asked the question, some 15 > minutes after asking it. You're right. And after re-reading my post, I described what the DNS mechanism is, not what the DNS Client service actually does. According to the OP.... "Apparently the DNS Client service optimizes the performance of DNS name resolution by storing previously resolved names in memory. If the DNS Client service is turned off, the computer can still resolve DNS names by using the upstream DNS servers." .....which makes the term DNS Client name somewhat of a misnomer, since the PC can still resolve using the specified DNS server....according to the text above anyway.....
From: Ace Fekay [MVP-DS, MCT] on 29 Mar 2010 01:18 "Jonathan de Boyne Pollard" <J.deBoynePollard-newsgroups(a)NTLWorld.COM> wrote in message news:IU.D20100327.T213623.P2445.Q0(a)J.de.Boyne.Pollard.localhost... > Why not research your problem before posting, instead of posting revised messages every ten minutes? > > I just remembered WHY I set the DNS Client service to Manual. I have a huge hosts file (with spam blocking). I don't remember the problem but that is why I disabled the DNS Client service. > > So my question has morphed to ... > > What does the DNS Client service actually do (besides slowing down huge hosts files and prevening network repairs)? > > Actually, the DNS Client speeds up things when one has huge hosts files. Without the DNS Client service, the hosts file is read and processed by every individual application process for every individual query. With the DNS Client service, the hosts file is read and processed once, by the DNS Client service at startup, and then re-read whenever the DNS Client service sees that it has changed. > I agree. In a nutshell, the DNS Client service is the caching service. :-) -- Ace This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution. Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft MVP - Directory Services If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
From: Kat Rabun on 29 Mar 2010 03:52 On Mon, 29 Mar 2010 01:18:31 -0400, Ace Fekay [MVP-DS, MCT] wrote: > I agree. In a nutshell, the DNS Client service is the caching service. The strange thing is that almost everyone on the net recommends we turn OFF the DNS Client (aka DNS Caching) services, especially for people (like me) who have a huge hosts file. That doesn't jive with the explanation given about why DNS Client (i.e., caching) is useful for large hosts file. I'm very confused! REFERENCES: "The most important thing to do before using large HOSTS files is to disable the DNS Client" http://www.ericphelps.com/scripting/samples/Hosts/index.htm "We recommend disabling the "DNS Client" service on all local computers" http://www.simpledns.com/kb.aspx?kbid=1089 "Turn off the "DNS Client" service entirely. This is What we are recommending!" http://grandcountyinternet.com/DNSResolverCache/ "To avoid the slowdown, either disable the DNS Client or avoid using a large HOSTS file" http://smallvoid.com/article/winnt-services-dnscache.html "Disable caching of unsuccessful ("negative") DNS lookups" http://forums.mozillazine.org/viewtopic.php?t=5501 "Unless you are accessing network filesystems and databases, disable the DNS Client" http://www.jasonn.com/turning_off_unnecessary_services_on_windows_xp etc. Even Microsoft weighs in, albeit not as strongly as the rest of the world! "DNS caching ... may generate a false impression that DNS "round robin" http://support.microsoft.com/kb/318803
|
Next
|
Last
Pages: 1 2 3 Prev: BEWARE OF AT&T! Next: Mis-using DNS for solving WWW browser problems. |