CONSTANT DNS flushes required

Follow
Avatar
jkluttz

Does anyone know what would cause me to have to CONTINUALLY (up to several times in an hour) flush the DNS cache?  Until I do this I get "name resolution failed," blank pages, pages with missing images, etc.  Once I clean (for the umpteenth time) it goes back to working.  This is not something I can live with --- nor is leaving my kids to the whiles of every dark corner of internet Mordor.  Very frustrating issue.

1

Comments

6 comments

Sort by Date Votes
  • Avatar
    rotblitz

    This does not look like it is OpenDNS related, or DNS related at all.  It merely seems to be a problem with your OS, your browser or your internet connection.

    Also, what exactly are you referring to with "DNS cache"?  Is this your local resolver cache or your browser cache?

    0
    Comment actions Permalink
  • Avatar
    jkluttz

    The DNS resolver cache (ipconfig/flushdns).  I'm posting here - and assuming this is a DNS issue - for these reasons:  1- The problem began after I setup my OpenDNS account.  2- The error I receive is "name resolutions failed."  3.  When I change my DNS back to my ISP - or to Google - I have no issues.  

    I ran Google DNS (8.8.8.8) for a month without a single issue.  Changed back to OpenDNS and it immediately began failing again.  I can browse without issue for a minute or two and then I'm unable to resolve names.  If I flush the resolver cache it will work again for another few minutes.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Ok, post the complete plain text output of the following commands:

    nslookup -type=txt debug.opendns.com.
    tracert 208.67.222.222
    tracert 208.67.220.220

    0
    Comment actions Permalink
  • Avatar
    jkluttz

    Text is below.  However - let me note that I manually entered the DNS in my local computer network settings and that very well may have eliminated the issue.  I've been without issue for maybe an hour - which is a good indication.

    Microsoft Windows [Version 6.3.9600]
    (c) 2013 Microsoft Corporation. All rights reserved.

    C:\Users\Jeff>nslookup -type=txt debug.opendns.com
    Server: resolver1.opendns.com
    Address: 208.67.222.222

    Non-authoritative answer:
    debug.opendns.com text =

    "server 11.dfw"
    debug.opendns.com text =

    "flags 20 0 2b6 4003e00000804c3"
    debug.opendns.com text =

    "id 13543289"
    debug.opendns.com text =

    "source 76.164.79.85:61067"

    Microsoft Windows [Version 6.3.9600]
    (c) 2013 Microsoft Corporation. All rights reserved.

    C:\Users\Jeff>tracert 208.67.222.222

    Tracing route to resolver1.opendns.com [208.67.222.222]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 22 ms 25 ms 24 ms wddl-10k-lo100-primary.consolidated.net [207.70.
    184.110]
    3 24 ms 25 ms 25 ms wddl-cor1-ge5-1.consolidated.net [207.70.184.161
    ]
    4 25 ms 23 ms 25 ms wddl-bdr-7606-te4-2.consolidated.net [207.70.184
    .230]
    5 102 ms 215 ms 27 ms te2-2.ccr01.iah04.atlas.cogentco.com [38.122.156
    .45]
    6 23 ms 26 ms 24 ms te0-3-0-3.ccr22.iah01.atlas.cogentco.com [154.54
    .47.13]
    7 30 ms 29 ms 33 ms be2146.ccr22.dfw01.atlas.cogentco.com [154.54.25
    .242]
    8 33 ms 31 ms 32 ms be2032.ccr21.dfw03.atlas.cogentco.com [154.54.6.
    54]
    9 34 ms 32 ms 36 ms 4.68.111.101
    10 33 ms 33 ms 32 ms ae-4-90.edge5.Dallas3.Level3.net [4.69.145.209]

    11 33 ms 32 ms 32 ms OPEN-DNS-IN.edge5.Dallas3.Level3.net [4.59.36.11
    8]
    12 33 ms 34 ms 32 ms resolver1.opendns.com [208.67.222.222]

    Trace complete.

    C:\Users\Jeff>tracert 208.67.220.220

    Tracing route to resolver2.opendns.com [208.67.220.220]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 23 ms 23 ms 22 ms wddl-10k-lo100-primary.consolidated.net [207.70.
    184.110]
    3 23 ms 24 ms 23 ms wddl-cor1-ge1-9.consolidated.net [207.70.184.137
    ]
    4 23 ms 25 ms 24 ms wddl-bdr-7606-te4-2.consolidated.net [207.70.184
    .230]
    5 29 ms 26 ms 25 ms te2-2.ccr01.iah04.atlas.cogentco.com [38.122.156
    .45]
    6 28 ms 24 ms 24 ms te0-3-0-3.ccr22.iah01.atlas.cogentco.com [154.54
    .47.13]
    7 35 ms 31 ms 32 ms be2146.ccr22.dfw01.atlas.cogentco.com [154.54.25
    .242]
    8 32 ms 30 ms 31 ms be2032.ccr21.dfw03.atlas.cogentco.com [154.54.6.
    54]
    9 33 ms 72 ms 36 ms 4.68.111.101
    10 * 33 ms * ae-4-90.edge5.Dallas3.Level3.net [4.69.145.209]

    11 36 ms 33 ms 32 ms OPEN-DNS-IN.edge5.Dallas3.Level3.net [4.59.36.11
    8]
    12 34 ms 34 ms 31 ms resolver2.opendns.com [208.67.220.220]

    Trace complete.

    1
    Comment actions Permalink
  • Avatar
    rotblitz

    Fine, I can see no problems.  You configured the OpenDNS resolver addresses on your computer,  You're using the Dallas OpenDNS location, and your IP address 76.164.79.85 is registered with OpenDNS network ID 13543289.  Your latency to the OpenDNS servers is still good.

    "let me note that I manually entered the DNS in my local computer network settings"

    This may well be the reason why it works.  If you configured the resolver addresses on the router before, many routers are really lousy DNS servers and forwarders.  This has been reported before.  In this case it is better to let the computer do the DNS forwarder job as you did, not the router.

    If you want to use the router for DNS nevertheless, try with a firmware upgrade (or downgrade), or flash the router with an alternative firmware, or use another router.

    1
    Comment actions Permalink
  • Avatar
    jkluttz

    Given all the facts, I think you are correct.  I stepped out of the office for a while - but having just gotten back everything is still working fine.  It must simply be the router doing a poor job of handling the DNS requests.

    Thanks for your time.  I'm happy to have a solution.

     

    0
    Comment actions Permalink

Please sign in to leave a comment.