Hi,
In my company, we currently experiencing some dns issues for internal resolution in our guest vm (windows) only in shared network.
If we configure our guest vm in bridge network, we do not have this dns issue.
Moreover in shared network, this issue is not permanent, sometime it works fine, and few time it does not.
We are using :
- the latest parallels version : 13.3.0 (43321)
- guest vm : Windows 10 pro
When I have this issue, I cannot do any internal dns resolution, the ping is still working fine with direct ip but not with dns alias.
I tried nslookup, and the default dns server 10.211.55.1 with shared network is not able to resolve those internal dns alias.
On my mac side, I have no issue at all, in the same moment, I am able to ping and resolve internal dns alias.
So on parallels, here are what I have done :
- disable ipv6 on my shared network card
- went in mac system preferences -> shared network card -> advanced -> DNS and configure directly our internal dns servers there and internal search domain
Is it a good workaround ?
Does someone experience the same dns resolution issue in a parallels guest vm configured on shared network ?
Thanks a lot for your help,
Denis.
Click to expand...