DNS Benchmark on Apple Silicon Parallels Win11 ARM no Internet Access?

  • 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!

    /Steve.
  • 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.)

Dpace23236

New member
Feb 15, 2024
4
0
Just downloaded DNS Benchmark and ran on a Windows 11 ARM on Parallels on Apple Silicon MacBook. Starts up fine but then complains "Internet DNS Access Trouble". The VM has full Internet Access, and browsers and Outlook work fine. I have tried running as Administrator and also turned on Compatibility Mode but nothing makes any difference. What am I missing here?
 
Hard to say. Too many variables to eliminate to figure out which software component is failing. If Windows is accessing the Internet correctly, presumably it's able to resolve DNS properly as well. It could be that Parallels is doing something "magical" as a proxy that the DNS Benchmark doesn't like. Start by checking if the DNS configuration inside windows makes sense for you.

Start by you bringing up a CMD window on the Windows 11 machine and entering nslookup. It should output something containing values you would recognize. It may help you recognize if it's your preferred DNS or if it looks like a proxy in Parallels.

Code:
Default Server:  {some value}
Address:  {some IP address}

You don't have a problem so it should work, but for kicks check by entering some host names, like www.google.com and see that you get a result back that makes sense. Enter exit when you're done.
 
Hard to say. Too many variables to eliminate to figure out which software component is failing. If Windows is accessing the Internet correctly, presumably it's able to resolve DNS properly as well. It could be that Parallels is doing something "magical" as a proxy that the DNS Benchmark doesn't like. Start by checking if the DNS configuration inside windows makes sense for you.

Start by you bringing up a CMD window on the Windows 11 machine and entering nslookup. It should output something containing values you would recognize. It may help you recognize if it's your preferred DNS or if it looks like a proxy in Parallels.

Code:
Default Server:  {some value}
Address:  {some IP address}

You don't have a problem so it should work, but for kicks check by entering some host names, like www.google.com and see that you get a result back that makes sense. Enter exit when you're done.
Well NSLOOKUP worked, sort of, first sample below with no changes yet. I then changed Parallels Network setting from its recommended setting of "Shared Network (Recommended)" to "Bridged Network (WiFi)" and then DNS Benchmark worked. It also added IPV6 addresses as you can see below after the change. I don't understand why it won't work when everything else worked properly in Parallels default Network setting?

NSLOOKUP result BEFORE CHANGE...

> google.com
Server: UnKnown
Address: 10.211.55.1

Non-authoritative answer:
Name: google.com
Address: 142.251.35.174

> apple.com
Server: UnKnown
Address: 10.211.55.1

Non-authoritative answer:
Name: apple.com
Address: 17.253.144.10

NSLOOKUP result AFTER change...

nslookup google.com
Server: Pace-Main
Address: 10.238.235.164

Non-authoritative answer:
Name: google.com
Addresses: 2607:f8b0:4004:c0b::8a
2607:f8b0:4004:c0b::65
2607:f8b0:4004:c0b::66
2607:f8b0:4004:c0b::71
142.250.31.102
142.250.31.113
142.250.31.138
142.250.31.139
142.250.31.100
142.250.31.101
 
I don't understand why it won't work when everything else worked properly in Parallels default Network setting?
This would seem to be a question to ask the support folks at Parallels. It seems there is a technological difference between "shared" and "bridged". It seems it's like I suspected, the shared mode is doing some sort of proxy of the DNS while the bridged mode is not.
 
@Dpace23236:

PLEASE be sure to bring this up again once the Benchmark has entered its final pre-release stage. At this point too much is in flux. But this is the sort of thing I'll be glad to dig into — and actively wanting to dig into — once we have broadly finished features and functions. Thanks!