DNS resolution fails in all VMs

T

toonetown

Member
It seems since upgrading to 19.1.0, almost daily, DNS resolution stops working within all my VMs. This can be fixed by closing all my VMs, and running `prlsrvctl stop` and then relaunching the VMs...but it kind of gets annoying to need to restart the DNS service each day.

This seems to be something related to the DNS server that Parallels runs on the host machine. When it is hit, all VMs are impacted (regardless of the OS of the VM) until the server is restarted.

Is there something I'm doing that's causing this to happen?
 
toonetown said:
It seems since upgrading to 19.1.0, almost daily, DNS resolution stops working within all my VMs. This can be fixed by closing all my VMs, and running `prlsrvctl stop` and then relaunching the VMs...but it kind of gets annoying to need to restart the DNS service each day.

This seems to be something related to the DNS server that Parallels runs on the host machine. When it is hit, all VMs are impacted (regardless of the OS of the VM) until the server is restarted.

Is there something I'm doing that's causing this to happen?
Click to expand...

Hello toonetown,

To aid us in troubleshooting this further, please collect a technical report while the issue is being reproduced (click the Parallels icon > Help > Send technical data > check "Attach screenshots..." > press Send Report) and send the report's 9-digit ID in reply to this post.
 
Is there any way to get an update on the technical report that was sent in? This issue is happening each evening and it preventing a broader rollout of Parallels within our environment.
 
This issue has reared it's ugly head again after upgrading to Parallels 27 and Golden Gate (on my host machine).

The same workaround solution addresses the issue for me - I needed changed the value of `StartNaptd` to `0` in `/Library/Preferences/Parallels/network.desktop.xml` and restarted parallels.

I did notice a pattern this time...network would work just fine in my windows VM _until_ I launched a macOS VM. Then I'd lose network connectivity in _ALL_ VMs (even ones launched after doing that). After making the `StartNaptd` change, I have not encountered the issue.

(For reference - in case anyone from Parallels encounters this message and wants to look into it, the original case I logged where we discussed StartNaptd was case number 4507570 - and the same solution worked for me in this case, even though I'm now on an Apple Silicon Mac)
 
You must log in or register to reply here.
Back
Top