Page 2 of 3 FirstFirst 123 LastLast
Results 21 to 40 of 48

Thread: WinXP won't clear the DNS cache (can it be cleared manually)?

  1. #21
    Kat Rabun
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    On Sun, 28 Mar 2010 02:27:22 -0700, John Corliss wrote:

    > I'm going to change it ... because it's better syntax.


    Just for the record, I had tried the following commands in WinXP SP3; but
    both failed due to the fact that the listing and flushing of the DNS cache
    cannot be accomplished without the "DNS Client" service running.

    C:\> ipconfig /displaydns
    C:\> ipconfig /flushdns

    This is what I previously reported for those commands (before enabling the
    otherwise unnecessary DNS Client service).

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    C:\Documents and Settings\kathleen>ipconfig /flushdns
    Windows IP Configuration
    Could not flush the DNS Resolver Cache: Function failed during execution.

    C:\Documents and Settings\kathleen>ipconfig /displaydns
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    Windows IP Configuration

    www.adserver.com
    ----------------------------------------
    Record Name . . . . . : www.adserver.com
    Record Type . . . . . : 1
    Time To Live . . . . : 595859
    Data Length . . . . . : 4
    Section . . . . . . . : Answer
    A (Host) Record . . . : 127.0.0.1

    yieldmanager.net
    ----------------------------------------
    Record Name . . . . . : yieldmanager.net
    Record Type . . . . . : 1
    Time To Live . . . . : 595859
    Data Length . . . . . : 4
    Section . . . . . . . : Answer
    A (Host) Record . . . : 127.0.0.1

    www.adtrak.net
    ----------------------------------------
    Record Name . . . . . : www.adtrak.net
    Record Type . . . . . : 1
    Time To Live . . . . : 595859
    Data Length . . . . . : 4
    Section . . . . . . . : Answer
    A (Host) Record . . . : 127.0.0.1


    BTW, I also found out how to start and stop the DNS caching:
    c:\> net stop dnscache
    c:\> sc servername stop dnscache

  2. #22
    Johnw
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    Kat Rabun formulated the question :
    > This is what I previously reported for those commands (before enabling the
    > otherwise unnecessary DNS Client service).
    >

    The DNS cache is cleared at every reboot.

    XP Myths - Myths Regarding Windows XP
    http://mywebpages.comcast.net/SupportCD/XPMyths.html

    Services - Disabling Negative
    Myth - "Disabling certain Services improves performance."
    Reality - "Disabling certain Services actually reduces performance."
    Automatic DNS Client Service - "The overall performance of the client
    computer decreases and the network traffic for DNS queries increases if
    the DNS resolver cache is deactivated. This effectively reduces
    Internet Performance for sites you have previously visited and puts an
    unnecessary load on your ISP's DNS server."

    Large Hosts Files
    "Large Hosts Files cause Internet related slowdowns due to DNS Client
    Server Caching. This negatively effects your browsing speed.
    AntiSpyware Hosts File authors irresponsibly recommend disabling the
    DNS Client Service to solve this problem. This is not a solution. The
    overall performance of the client computer decreases and the network
    traffic for DNS queries increases if the DNS resolver cache is
    deactivated. This effectively reduces Internet Performance for sites
    you have previously visited and puts an unnecessary load on your ISP's
    DNS server."
    Notes - There is a much better solution for bad site blocking using
    SpywareBlaster which more intelligently use's Internet Explorer's
    built-in Zone Security settings and the registry. Mozilla/Firefox
    protection is also provided.



  3. #23
    DanS
    Guest

    Re: What does the DNS Client service actually do?

    Jonathan de Boyne Pollard
    <J.deBoynePollard-newsgroups@NTLWorld.COM> wrote in
    news:IU.D20100328.T083553.P504.Q0@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.....


  4. #24
    John Corliss
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    Johnw wrote:
    > Kat Rabun formulated the question :
    >> This is what I previously reported for those commands (before enabling
    >> the
    >> otherwise unnecessary DNS Client service).
    >>

    > The DNS cache is cleared at every reboot.
    >
    > XP Myths - Myths Regarding Windows XP
    > http://mywebpages.comcast.net/SupportCD/XPMyths.html
    >
    > Services - Disabling Negative
    > Myth - "Disabling certain Services improves performance."
    > Reality - "Disabling certain Services actually reduces performance."
    > Automatic DNS Client Service - "The overall performance of the client
    > computer decreases and the network traffic for DNS queries increases if
    > the DNS resolver cache is deactivated. This effectively reduces Internet
    > Performance for sites you have previously visited and puts an
    > unnecessary load on your ISP's DNS server."


    Thanks for that info. I was, of course, unaware of this. I do leave the
    DNS Client Service running though. Just made sense to me that I should.
    Also, BlackViper pretty much recommends that you do so:

    http://www.blackviper.com/WinXP/servicecfg.htm

    > Large Hosts Files
    > "Large Hosts Files cause Internet related slowdowns due to DNS Client
    > Server Caching. This negatively effects your browsing speed. AntiSpyware
    > Hosts File authors irresponsibly recommend disabling the DNS Client
    > Service to solve this problem. This is not a solution. The overall
    > performance of the client computer decreases and the network traffic for
    > DNS queries increases if the DNS resolver cache is deactivated. This
    > effectively reduces Internet Performance for sites you have previously
    > visited and puts an unnecessary load on your ISP's DNS server."
    > Notes - There is a much better solution for bad site blocking using
    > SpywareBlaster which more intelligently use's Internet Explorer's
    > built-in Zone Security settings and the registry. Mozilla/Firefox
    > protection is also provided.


    I've observed this myself. I think Spybot S&D's "Immunize" feature
    increases the size of your hosts file. I no longer run that program though.

    --
    John Corliss BS206. I block all Google Groups posts due to Googlespam,
    and as many posts from anonymous remailers (like x-privat.org for eg.)
    as possible due to forgeries posted through them.

    No ad, CD, commercial, cripple, demo, nag, share, spy, time-limited,
    trial or web wares OR warez for me, please. Adobe Flash sucks, DivX rules.

  5. #25
    Dave Warren
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    In message <hola76$j43$1@tioat.net> Kat Rabun
    <katspianostudioXXX@Use-Author-Supplied-Address.invalid> was claimed to
    have wrote:

    >On Sat, 27 Mar 2010 15:33:01 +0000 (UTC), Kat Rabun wrote:
    >
    >> What does the DNS Client actually do (besides preventing a network repair)?

    >
    >For my type of home network, the DNS Client service doesn't appear to do
    >anything useful! :(
    >
    >I have a giant hosts file which I update daily as I run into web sites I
    >feel act suspiciously (malware, javaware, flashware, annoying popups,
    >etc.). I also remove duplicate entries programatically (unixutils "sort
    >-u").
    >
    >In my home network, all the Windows XP SP3 DNS Client seems to (really) do
    >is just two bad things:
    >- The DNS Client prevent network repairs (by preventing DNS flushes)
    >- The DNS Client foul ups systems with large hosts files
    >
    >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.


    DNS Client also caches the contents of the HOSTS file, otherwise every
    single DNS lookup goes through the file line by line looking for
    comparisons.

    If you have local, fast, reliable DNS servers and a trivial HOSTS file,
    DNS Client adds little benefit. However, if you have a large HOSTS
    file, DNS Client speeds up lookups significantly. Similarly, if you
    have unreliable DNS servers, or your DNS servers are more than a few
    milliseconds away, DNS Client can create a significantly snappier user
    experience.

  6. #26
    Dave Warren
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    In message <hol8fd$ili$1@tioat.net> Kat Rabun
    <katspianostudioXXX@Use-Author-Supplied-Address.invalid> was claimed to
    have wrote:

    >On Sat, 27 Mar 2010 08:07:36 -0700, Kat Rabun wrote:
    >
    >> What could be preventing the DNS cache from flushing?

    >
    >I found the problem was the "DNS Client" service wasn't running.
    >
    >I hadn't been running the DNS Client service ever since I set the DNS
    >CLient to "Manual" as per a web site months, or maybe even years ago, which
    >said to disable all unnecessary and unneeded Windows XP services.
    >
    >Since the Internet connection has been working all that time (the router
    >automatically assigns the DNS to the computer in the home network), I
    >wonder what usful thing the DNS Client does???
    >
    >What does the DNS Client actually do (besides preventing a network repair)?


    DNS Client doesn't "prevent a network repair" but rather, it's part of
    the network repair process. By disabling parts of Windows randomly, you
    should be prepared for unexpected behaviour when performing activities
    that rely on those disabled components.

  7. #27
    Harry331
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    Kat Rabun wrote...
    >
    >In WinXP SP3 "Network Connections", I right click "Repair" the wired "Local
    >Area Connection" but always get an error. How do I clear the DNS cache?
    >
    >Here is the error I always get (even after rebooting):
    >
    > Repair Local Area Connection
    > Windows could not finish repairing the problem because the
    > following action cannot be completed:
    > Clearing the DNS cache
    > For assistance, contact the person who manages your network.
    >
    >Unfortunately, I am the person who "manages" the home network.
    >
    >How do I repair an Internet connection that won't release the dns cache?
    >(I have a similar problem with the wireless connection which it won't
    >release)


    Not sure if the following help.

    c:\> ipconfig /flushdns

    Windows IP Configuration

    Successfully flushed the DNS Resolver Cache.

    c:\>


  8. #28
    Ace Fekay [MVP-DS, MCT]
    Guest

    Re: What does the DNS Client service actually do?

    "Jonathan de Boyne Pollard" <J.deBoynePollard-newsgroups@NTLWorld.COM> wrote in message news:IU.D20100327.T213623.P2445.Q0@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.

  9. #29
    Ace Fekay [MVP-DS, MCT]
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    "Kat Rabun" <katspianostudioXXX@Use-Author-Supplied-Address.invalid> wrote in message news:hom71v$qp9$1@tioat.net...
    > On Sat, 27 Mar 2010 14:35:18 -0500, Char Jackson wrote:
    >
    >> My question would be, what problem are you having that is causing you
    >> to try to repair the connection?

    >
    > Every once in a while (maybe once a week or once every few weeks or so),
    > the wireless Internet connection goes "down" on the PC.
    >
    > When I "repair" it, it comes back "up".
    >
    > I don't really know more than that ... but I've found now that setting the
    > DNS Client to "manual" is what caused the wireless connection to not be
    > able to be repaired. It repairs now that I've started the DNS Client
    > manually.
    >
    > I wonder whether most people follow the recommendation to disable
    > unnecessary services such as the "DNS Client"?



    Where did you get that recommendation from? And based on where you got it from, what was the recommendation based on? Were you having a resolution problem, or infected with a virus that was affecting the resolver algorithm?

    --
    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.

  10. #30
    Kat Rabun
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    On Mon, 29 Mar 2010 01:20:00 -0400, Ace Fekay [MVP-DS, MCT] wrote:

    >> I wonder whether most people follow the recommendation to disable
    >> unnecessary services such as the "DNS Client"?

    > Where did you get that recommendation from?


    Everywhere I looked, people strongly advise disabling DNS caching!

    "The most important thing to do before using large HOSTS files is to
    disable the DNS Client"
    http://www.ericphelps.com/scripting/...osts/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-s...-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_un..._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

  11. #31
    Kat Rabun
    Guest

    Re: What does the DNS Client service actually do?

    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/...osts/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-s...-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_un..._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


  12. #32
    Char Jackson
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    On Mon, 29 Mar 2010 07:49:18 +0000 (UTC), Kat Rabun
    <katspianostudioXXX@Use-Author-Supplied-Address.invalid> wrote:

    >On Mon, 29 Mar 2010 01:20:00 -0400, Ace Fekay [MVP-DS, MCT] wrote:
    >
    >>> I wonder whether most people follow the recommendation to disable
    >>> unnecessary services such as the "DNS Client"?

    >> Where did you get that recommendation from?

    >
    >Everywhere I looked, people strongly advise disabling DNS caching!


    That's strange, do any of the links you provided actually recommend
    disabling DNS caching? They don't seem to be recommending that at all.

    >"The most important thing to do before using large HOSTS files is to
    >disable the DNS Client"
    >http://www.ericphelps.com/scripting/...osts/index.htm


    So don't use a large Hosts file. Problem solved.
    (I didn't check this link.)

    >"We recommend disabling the "DNS Client" service on all local computers"
    >http://www.simpledns.com/kb.aspx?kbid=1089


    This advice only applies if you're running their DNS Plus application.

    >"Turn off the "DNS Client" service entirely. This is What we are
    >recommending!"
    >http://grandcountyinternet.com/DNSResolverCache/


    Two problems with this one. First, it's from 2002, and second, and
    even more importantly, it's from John Navas. I wouldn't take advice
    from John Navas.

    >"To avoid the slowdown, either disable the DNS Client or avoid using a
    >large HOSTS file"
    >http://smallvoid.com/article/winnt-s...-dnscache.html


    So don't use a large Hosts file. Problem solved.
    (I didn't check this link.)

    >"Disable caching of unsuccessful ("negative") DNS lookups"
    >http://forums.mozillazine.org/viewtopic.php?t=5501


    This seems to be a user forum where a couple of folks are reporting a
    gut reaction that doesn't seem to be supported by any facts; i.e.,
    disabling the DNS Client service dramatically increases page rendering
    time. Extremely doubtful, especially without any benchmarks to back up
    the claims.

    >"Unless you are accessing network filesystems and databases, disable the
    >DNS Client"
    >http://www.jasonn.com/turning_off_un..._on_windows_xp


    The comment from this page is "Comment: It's typically good to leave
    this on.".

    >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


    Last but not least, this KB article doesn't make any kind of blanket
    recommendation about disabling the DNS Client service.

    In summary, I don't see any reason to disable it at all.


  13. #33
    Kat Rabun
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    On Mon, 29 Mar 2010 04:57:14 -0500, Char Jackson wrote:

    >>Everywhere I looked, people strongly advise disabling DNS caching!

    >
    > That's strange, do any of the links you provided actually recommend
    > disabling DNS caching? They don't seem to be recommending that at all.
    > In summary, I don't see any reason to disable it at all.


    I'm now thoroughly confused. :(

    I thought disabling DNS Caching or disabling the DNS Client service are,
    essentially, the same thing.

    These articles "seemed" to recommend disabling one or the other (which, I
    thought, was the same thing).

    I do understand your comments (and I don't disagree as I don't have enough
    information, e.g., who is John Navas, etc.); yet, I do make daily use of a
    very large hosts file (and for good reason).

    So, I enabled the DNS Client service (as per recommendations here).

    However, I just realized I also use Comodo which has an option to use THEIR
    DNS servers.

    Do you think this "feature" is partially the cause of what we're seeing?

  14. #34
    Kat Rabun
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    On Mon, 29 Mar 2010 10:33:22 +0000 (UTC), Kat Rabun wrote:

    > So, I enabled the DNS Client service (as per recommendations here).
    >
    > However, I just realized I also use Comodo which has an option to use THEIR
    > DNS servers.
    >
    > Do you think this "feature" is partially the cause of what we're seeing?


    This is Comodo's description of the "Comodo Secure DNS Configuration"
    feature!

    Comodo Secure DNS - Another free service intended to provide you with
    a safer, smarter, and faster Internet:
    - Websites load faster because your domain name requests are resolved by
    our worldwide network of fully redundant DNS servers
    - Highly secure infrastructure reduces your exposure to DNS Cache Poisoning
    attacks
    - Parked, not in use, or commonly misspelled domains are automatically
    detected and forwarded

    If you use Comodo Secure DNS Servers:
    - Your computer's primary/secondary DNS settings will be changed to
    156.154.70.22, 156.154.71.22
    If you are in a corporate network or using VPN connections, then contact
    your administrator before enabling this option to avoid potential
    connectivity issues.

  15. #35
    Ace Fekay [MVP-DS, MCT]
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    "Kat Rabun" <katspianostudioXXX@Use-Author-Supplied-Address.invalid> wrote in message news:hopvtf$ur7$1@tioat.net...
    > On Mon, 29 Mar 2010 10:33:22 +0000 (UTC), Kat Rabun wrote:
    >
    >> So, I enabled the DNS Client service (as per recommendations here).
    >>
    >> However, I just realized I also use Comodo which has an option to use THEIR
    >> DNS servers.
    >>
    >> Do you think this "feature" is partially the cause of what we're seeing?

    >
    > This is Comodo's description of the "Comodo Secure DNS Configuration"
    > feature!
    >
    > Comodo Secure DNS - Another free service intended to provide you with
    > a safer, smarter, and faster Internet:
    > - Websites load faster because your domain name requests are resolved by
    > our worldwide network of fully redundant DNS servers
    > - Highly secure infrastructure reduces your exposure to DNS Cache Poisoning
    > attacks
    > - Parked, not in use, or commonly misspelled domains are automatically
    > detected and forwarded
    >
    > If you use Comodo Secure DNS Servers:
    > - Your computer's primary/secondary DNS settings will be changed to
    > 156.154.70.22, 156.154.71.22
    > If you are in a corporate network or using VPN connections, then contact
    > your administrator before enabling this option to avoid potential
    > connectivity issues.




    Kat, read my responses to those links. In addition to Char's responses, which I agree with, you should really leave the service alone. I made some other recommendations.

    And good question about your scenario. Is this a home machine, or a machine on a corp network?

    Ace

  16. #36
    Char Jackson
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    On Mon, 29 Mar 2010 10:33:22 +0000 (UTC), Kat Rabun
    <katspianostudioXXX@Use-Author-Supplied-Address.invalid> wrote:

    >On Mon, 29 Mar 2010 04:57:14 -0500, Char Jackson wrote:
    >
    >>>Everywhere I looked, people strongly advise disabling DNS caching!

    >>
    >> That's strange, do any of the links you provided actually recommend
    >> disabling DNS caching? They don't seem to be recommending that at all.
    >> In summary, I don't see any reason to disable it at all.

    >
    >I'm now thoroughly confused. :(
    >
    >I thought disabling DNS Caching or disabling the DNS Client service are,
    >essentially, the same thing.
    >
    >These articles "seemed" to recommend disabling one or the other (which, I
    >thought, was the same thing).


    I hope someone will correct me if I'm wrong, but I assumed the DNS
    Client service performed local DNS caching as one of its duties, so in
    that respect they are related.

    >I do understand your comments (and I don't disagree as I don't have enough
    >information, e.g., who is John Navas, etc.); yet, I do make daily use of a
    >very large hosts file (and for good reason).
    >
    >So, I enabled the DNS Client service (as per recommendations here).
    >
    >However, I just realized I also use Comodo which has an option to use THEIR
    >DNS servers.
    >
    >Do you think this "feature" is partially the cause of what we're seeing?


    No, I don't think it's related. You can use an application called
    Namebench to test multiple DNS servers to see which are fastest for
    you. http://code.google.com/p/namebench/


  17. #37
    Kat Rabun
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    On Mon, 29 Mar 2010 09:09:24 -0400, Ace Fekay [MVP-DS, MCT] wrote:

    > And good question about your scenario.


    It's just a home machine. WinXP Home. Not much of a network at all. I just
    realized Comodo has its own DNS servers, which I enabled, to see if that
    helps.

  18. #38
    Ace Fekay [MVP-DS, MCT]
    Guest

    Re: WinXP won't clear the DNS cache (can it be cleared manually)?

    "Kat Rabun" <katspianostudioXXX@Use-Author-Supplied-Address.invalid> wrote in message news:hoqv53$7cc$1@tioat.net...
    > On Mon, 29 Mar 2010 09:09:24 -0400, Ace Fekay [MVP-DS, MCT] wrote:
    >
    >> And good question about your scenario.

    >
    > It's just a home machine. WinXP Home. Not much of a network at all. I just
    > realized Comodo has its own DNS servers, which I enabled, to see if that
    > helps.



    I'm not familiar with Comodo's DNS servers. You may want to try OpenDNS. I think that's a better solution than all of those entries in the hosts files slowing down your machine.

    And leave the DNS Client service running.

    Did you read my other response?

    --
    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.

  19. #39
    Jonathan de Boyne Pollard
    Guest

    Re: What does the DNS Client service actually do?



    The strange thing is that almost everyone on the net recommends we turn OFF the DNS Client (aka DNS Caching) services, [...]



    It's usually folk wisdom, that almost certainly has been passed on from each to the other.&nbsp; It's often not based upon knowledge of what the DNS Client does or is.&nbsp; (One person in your list there thinks that the DNS Client is a DNS server, for example.)&nbsp; It's instead based upon an Animal-Farm-like simplistic notion of&nbsp; "service enabled bad, service disabled good", which is of course wrong.&nbsp; A second person in your list even blames the DNS Client service for the facts that xyr several ISPs are not presenting the same views of the DNS namespace as each other, and that sometimes DNS lookups produce (gasp!) answers that say that a particular domain name doesn't exist.



    Interestingly, one of the items in your list is someone posting this piece of folk wisdom in a discussion forum and having it debunked by other people.&nbsp; As you note, what you'll find written by Microsoft doesn't support this folk wisdom, either.&nbsp; As M. Fekay says, Microsoft is right about its own software, here.&nbsp; There are some instances where Microsoft gets things wrong about its own products, usually resulting from the fact that it's a big company and in such companies the people who write the user documentation are sometimes not the people who develop the software, or from the fact that even people within Microsoft aren't immune from believing Internet/WWW-garnered erroneous received wisdom from time to time, but this particular instance isn't one of them.




    The most noteworthy item in your list is the documentation for Simple DNS Plus.&nbsp; That's the only one that you present that actually gives a sensible reason for not having the DNS Client service enabled: namely that Simple DNS Plus is a fully-fledged caching resolving proxy DNS server, and if one has one of those locally, having the extra caching in the DNS Client service on the same machine makes no sense.



    Further sensible advice is the advice that you're ignoring, but that you'll find equally widely disseminated: Don't use DNS for this task at all.&nbsp; It's the wrong tool.&nbsp; The DNS is not a tool for meeting WWW browsing customization needs. That's a lesson that the world learned in 2003.&nbsp; Use an advertisment-blocking HTTP proxy server; use a PAC script, or use one of the many WWW browser plug-ins that do what you want to do.



    There two lessons here:



    Folk wisdom is often based upon people using magic incantations and not really understanding what their computers do.



    Abusing the DNS to solve an HTTP problem is wrongheaded.


  20. #40
    Jonathan de Boyne Pollard
    Guest

    Re: Reasons to give Comodo's "free DNS service" a wide berth



    This is Comodo's description of the "Comodo Secure DNS Configuration" feature!



    Here's a tip: Sales pitches are often not technically accurate.&nbsp; It's advertising, for goodness' sake.

    Websites load faster because your domain name requests are resolved by our worldwide network of fully redundant DNS servers

    DNS lookup is often not the major factor in the speed for which a "page" is loaded by a WWW browser.&nbsp; And a "worldwide network" is flim-flammery.&nbsp; All that the "worldwide network" achieves is putting the proxy DNS server relatively close to you.&nbsp; But you can put it even closer still by the simple expedients of doing things the way that most people do, and obtaining proxy DNS service in the ways outlined later.&nbsp; Ironically, the sales pitch is trying to sell you on benefit of the attempt to compensate for the fact that normally such a service is at a distance disadvantage to how one would normally obtain proxy DNS service.


    Highly secure infrastructure reduces your exposure to DNS Cache Poisoning attacks

    So, too, does running an ordinary DNS server in accordance with best current practice.&nbsp; Running an instance of Microsoft's DNS server for Windows, properly configured, locally, does the same, but with the benefit that it doesn't hand the keys to the kingdom to someone that you have no reason to trust (more on which later).

    Parked, not in use, or commonly misspelled domains are automatically detected and forwarded

    This is actually a bad thing.&nbsp; Again, the world learned this lesson in 2003.&nbsp; In addition to my Frequently Given Answer, there are several technical reports that one can find that discuss the problems of automatically generating faked DNS data for mis-spelled and non-existent domain names.&nbsp; This is a huge reason for avoiding Comodo, if anything.&nbsp; Danger, Will Robinson!




    If you use Comodo Secure DNS Servers:



    Unsurprisingly, what's missing from the sales pitch is the fact that by configuring your machines to use a resolving proxy DNS server from someone like this you are basically handing over full control of your view of the DNS namespace to a third party with whom you have no contractual relationship.&nbsp; The places to obtain proxy DNS service are (a) your own proxy DNS servers that you run, or (b) the proxy DNS servers provided by someone with whom you have a contractal relationship for that service.&nbsp; And as you can see, Comodo isn't someone to trust at all, here.&nbsp; For starters, it wants hi-jack mis-spelled and non-existent domain names and force you to places of its choosing for those names.&nbsp; The Verisign Internet Coup of 2003 is a lesson to learn from.



Similar Threads

  1. Computers on home network cannot shared files on other net. comput
    By Dr. Dave in forum ms.public.windows.networking.wireless
    Replies: 10
    Last Post: 01-04-10, 10:24 PM
  2. Connection, sometimes fast sometimes slow...
    By blue4paper in forum General Broadband Forum
    Replies: 18
    Last Post: 11-12-09, 09:39 PM
  3. Fast Downloads, Problems Connecting
    By ztpkng in forum General Broadband Forum
    Replies: 6
    Last Post: 11-09-09, 12:06 PM
  4. Internet time-out
    By Eros in forum Networking Forum
    Replies: 3
    Last Post: 06-05-09, 03:21 AM
  5. Tweak DNS Errors Caching in Windows Vista?
    By Emerson222 in forum Broadband Tweaks Help
    Replies: 1
    Last Post: 04-25-09, 10:24 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •