Windows 8 DNSClient Internet Blockage and Fault Finding Logic

I know this is not a Linux issue (but you can prove your hardware is OK by booting your PC/laptop with Linux from a pen drive or similar), but as I use Windows also, and this is such an apparently major Windows Balls Up, I thought I would highlight it, having only just solved it for myself with research after 3 days! Gonna be lots of Win 8 laptop Xmas presents like this new HP A8 of mine, that will frustrate a few folk methinks…

The BEST answer here is….DUMP WINDOWS completely and install Mint instead! Do research first though if you have a nVidia graphics card though – they won't open their tech to linux so drivers can be an issue:

MS really don't do themselves any favours do they? They then wonder why people look to Linux, Apple, Chrome and others, and this fault appears inexcusable, as it is widely reported on many forums, but just flushing the DNS cache does not solve the issue permanently. I will show how that's done anyway, just so you know how I arrived at the permanent, stupidly simple fix eventually, but first you must share my pain!

Having not done much IT in the last 3 years, it was an opportunity to NOT throw the useless piece of shit out the window (though it was very nearly returned to the shop within hours!), and engage brain instead.

I am amazed how much tech common sense you lose when you don't do IT continuously, and this scenario is a good example – with many people online suffering similarly with this fault it seems, maybe through lack of thought, not purely lack of technical knowledge, necessarily. This was my problem for the first 2 days of config hassle, by assuming the worst case – that the thing had some hardware fault and would need returning ASAP.

This current DNS fault has been around since 2013 at least from what I have researched!!


Only MS could leave this unfixed for so long with NO update fix even as of this laptops birth (as the BIOS calls it…) on the 12/12/14, and after 1.3GB of updates. Pathetic.

It seems it is a DNS timeout issue that fills the cache, and can "SEEMINGLY" be fixed with a registry entry (NO!) – or possibly, stop the DNS client running (I try that later after this REGISTRY fix failed):

which you may want to try first:

before adding this data to the Win registry database:

dhumanes replied on November 6, 2014

  •  In reply to BeekeeperGA's post on August 14, 2014

    Hi all,

    I have the same problem. Finally solved. It's related with dns query time outs. You have to:

    1. Create a new registry entry: REG_MULTI_SZ (multi-line string)

    2.-  HKLM\System\CurrentControlSet\Services\dnscache\Parameters\DNSQueryTimeouts

    3.- Set 9 9 9 0

    Last point could be adjusted.





    I added it like this in my new, unfamiliar Win 8 desktop, which seems to work:

    Press Win Button + X, and choose Run, then type regedit:

    Open the tree down to:


    Add a new key

    Rename it DNSQueryTimeouts

    Edit the default key value to 9990 – according to that forum info.

    Exit the registry editor and reboot.

    Now, you should be able to open many browser pages without constantly clearing the DNS cache with:

    Then flushing it with:

    With so much junk and ads in web pages these days, it does not take long to fill the cache to where it seems to stop the browser page loading as it cannot further resolve IP numbers to names.

    You can prove this by putting just an IP address from the full cache in your browser address bar, when it won't open normally, and you find it still opens the page:

    When something new out the box does not work at its most basic level, it's disheartening, depressing, and loses you confidence in the manufacturer immediately (surely they test these new devices straight out the box…don't they??? Surely they would not let it to market with a MAJOR fault – would they…? ) and tends to make you think the worst – that you bought a lemon, so just get rid of it.

    This can put you on the wrong Fault Finding track from the start – "Assumption Is the Mother of All Fuckups"…ringing in my ears again now…

    Even with past experience of Windows abhorrent untested default state conditions – insecure OS/network settings, unfixed bugs, and time constrained release schedules meaning unchecked problems etc. – but thinking I would give them another go anyway – the fact it's hard to choose a good spec, cheaper laptop that is not Chrome/Cloud based, without Windows on it, and most of us already have a heavy investment in Windows through old software, familiarity etc. – I bought one anyway.

    I still did not suspect it would be the OS over the hardware first!? Hmm…wonder why that is? Must be going stupid in my old age…

    I have berated MS for decades for their business model of "let the public fault find for us, AND we'll make money from Tech Support in the process" which is a disgusting, if effective one, but I still did not think software over hardware as a first likelihood for problem cause…I know…unreal isn't it?

    I have never owned an HP device, so for some reason, I assumed it must their fault. Creatures of habit eh?

    OK, done all that and it STILL has not fixed the problem! So much for Google research. What next?

    The option I suggested above to do first – the clue is in the 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."

    Just disabling this Service from Auto has done the trick – THAT'S IT!! Duh…

    Now I can go back and delete the Registry entries I added before…

    So how did I arrive at this fix?

    • The first clue was that the machine itself worked fine when booted from a Linux pen drive.

    Now I know the hardware is fine.

    • The hardware in Windows works fine as I can attach to the router, and see the other net shares on the inside interface of NAT translation.

      Both the RJ45 connector and the WiFi drivers must be working

    • Turned off Mcafee (so Windows) firewall software

      No pages are now being blocked by firewall policy rules now it is off, so page blocking cannot be the cause

    • Pages load for up to about 3 tabs of browsers before no connection results.

      This shows DNS works at first for this PC, as well as NAT translation across the firewall.

      As all other machines work OK, I know it is not a router or NAT issue

    • Tested the browser with an IP address only, to show connectivity to the Internet is not a specific page issue.
    • Research Internet (on a working PC if necessary) to see what WIN 8 DNS issues are being reported by others
    • Don't get side tracked by others logic for re-installing drivers (you checked yours already!), or downloading 3rd party software claiming to fix the issue (dangerous).


    So, what's the difference between my Win7 PCs running fine using DNSClient and Win8 not?

    The Service description is the same for both, but Win 8 DNSClient has different dependencies, that I don't have the interest to investigate further…but I'd take a first guess at the Network Store Interface Service…?