DNSBenchmark everything red

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


Oct 10, 2020
Kind of confused here, all these servers show up in DNSBenchmark as not working. BUT PiHole on this same network is using google. I can manually configure clients with google or Q9 and they work. At first I ran DNSBenchmark in wine under ubuntu and got this result but tried it again in windows, same computer. I can reach these fine it seems, what gives?


Background; I've been running pfBlockerNg for ages but lately it's blocking some stuff I need, some of the lists now require subs and I'm getting alerts for it. Always thought the managemnt of pfBlocker was a hassle too, so I thought I would return to PiHole for a little while as I like it's UI. I spun up a new VM in my ESXi box and stuck PiHole on it. Changed my DHCP DNS entry to the PiHole and clients are using it and things are working, client DHCP shows only the PiHole for DNS.
Answer; somewhere along the lines either I or pfBlocker added redirect rules to force DNS to pfBlocker. Those don't get removed when pfBlocker is removed, making me think I added them and forgot about them. The real mystery is how was pihole able to resolve if all that was blocked.
Last edited: