This system has NO nameservers configured for its use.

[GreenWine]

Hi again,

I have run the benchmark twice using different settings and still get this error telling me I have no nameservers configured, although I do. I have no connectivity issues and the benchmark is running fine.

On the first run my laptop was setup to use DNS from my router, in this case a google wifi hub using cloudflare 1.1.1.3.

On my second run, the laptop was setup to use NextDNS via the localhost command line tool which they provide for Linux.

I do also get some errors in the terminal whilst the benchmark is running, but they don't appear to be a problem. I would guess it's just popping up errors for certain resolvers not playing ball.

The only unusual thing is that I'm running Wine on Ubuntu.

 

[Steve]

Hi @GreenWine:

DNSB obtains the list of locally configured resolvers from Windows (or WINE). What happens if you do this:

1. Open the Add/Remove dialog.
2. Remove All Nameservers.
3. Add System's Nameservers.

This will clearly show you what the Windows API finds. If you do not see anything added when you "Add System's Nameservers" then DNSB is unable to pickup your machine's locally configured DNS resolvers so you'll need to add those yourself, manually.

Note that you can do this and make it automatic in the future by saving a "dnsbench.ini" (default name) file which will be seen and loaded whenever DNSB is started.

 

[peterblaise]

... versus NOT being able to save System as INI otherwise.

Second thoughts on that?

Thanks.

 

[Steve]

... versus NOT being able to save System as INI otherwise.

DNSB's deliberate exclusion of a system's resolvers from its .INI files won't be a problem for @GreenWine since the reason he would be adding his system resolvers to a custom list is because they are not being automatically found and identified as system resolvers by DNSB. Thus it will not exclude them from the INI save.

 

[GreenWine]

Hi @GreenWine:

DNSB obtains the list of locally configured resolvers from Windows (or WINE). What happens if you do this:

1. Open the Add/Remove dialog.
2. Remove All Nameservers.
3. Add System's Nameservers.

This will clearly show you what the Windows API finds. If you do not see anything added when you "Add System's Nameservers" then DNSB is unable to pickup your machine's locally configured DNS resolvers so you'll need to add those yourself, manually.

Note that you can do this and make it automatic in the future by saving a "dnsbench.ini" (default name) file which will be seen and loaded whenever DNSB is started.

Hi Mr G.

I cleared the nameserver list and then pressed add system ns and nothing happens, the table remains empty. No error pops up on the terminal when I push the button either.

When I press add default ns, the tool gets busy again populating it all.

Now what I didn't notice before is that when I first launch the benchmark, I get this error back behind on the terminal. Maybe this will be why it's not finding my DNS NS?


0128:err:winediag:ntlm_check_version ntlm_auth was not found. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
0128:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems


Not a problem for me, happy to add my current DNS manually (and I did and got a rather interesting result which I may share on another thread if it keeps occuring - in short though, my nextDNS result was SO fast compared to the others, it looked freaking impossible - which makes me think every previous dns test query was cached locally)

 

[Steve]

I cleared the nameserver list and then pressed add system ns and nothing happens, the table remains empty. No error pops up on the terminal when I push the button either.

Okay. That confirms that your WINE is not "seeing" your local resolvers. I'll ask over in the dev newsgroup whether this is true for everyone. Thanks!

 

[GreenWine]

I tried the tip from a listener to SN and tried using Steam to run the BM and it can see my local DNS servers, so in this aspect, an improvement over Wine.

 

[miquelfire]

Steam uses a fork of WINE called Proton. Its focus is for running Windows games on Linux. I think most of the extra stuff it has support for are things that might not matter to the likes of tools like this, but you never know.

 

[GreenWine]

Steam uses a fork of WINE called Proton. Its focus is for running Windows games on Linux. I think most of the extra stuff it has support for are things that might not matter to the likes of tools like this, but you never know.

Looks like Valve have taken Wine and used some of their infinite money to improve upon it.

 

[miquelfire]

That's basically it. Also, it helps they made a device that runs Linux but wanted their customers to be able to play as many games as possible on said device.

Because they're coming out with a device next year that runs on an ARM processor, they added running x86 apps on an ARM chip to Proton. I have seen talk about this support before they announced the device. Also, I'm not sure if a version of Proton has been released that allows normal people to test that bit yet.