Guests using NAT networking cannot resolve hostnames on Host's local LAN => Fixed in SVN

[mlueck]

VB: 5.x PUEL
Host OS: Xubuntu 14.04 x64
Guest OS's: Xubuntu 16.04 x64, Windows various versions

After VB build 5.0.20-106931, Guest OS's are no longer able to resolve DNS hostnames of hosts on the Host machine's local LAN when using NAT Guest network mode.

The 5.0.24 at least restored that functionality to Windows Guest VM's, however Ubuntu Linux Guest VM's are still impacted.

I rolled VB back to version 5.0.20-106931 and doing so restored the needed functionality for both Guest VM OS's.

Switching the VM networking setting to Bridge mode is a workaround to this issue using the .22 / .24 builds of VB. However I prefer to be using NAT Guest network mode.

The Host machine's local LAN DNS server has both a zone for the local LAN, and performs caching DNS for Internet names.

Please let me know what further information would be helpful to diagnose this regression defect.

[Valery Ushakov]

Please provide VBox.log file for the still affected Linux VM and for the Windows VM that now works with 5.0.24. Please, provide your /etc/resolv.conf file.

[mlueck]

Files for first request

[mlueck]

Please find just attached 15575_Req1.zip containing:

WinXP_VB5.0.20_nslookup.txt <-- NSLookup working
WinXP_VB5.0.20_VBox.log <-- The VBox log from that VM's execution
WinXP_VB5.0.24_nslookup.txt <-- NSLookup working - used to fail @ VBox 5.0.22
WinXP_VB5.0.24_VBox.log <-- The VBox log from that VM's execution
Xubuntu1604_resolv.conf <-- Xubuntu's resolv.conf pointed back at the local DNS cache daemon
Xubuntu1604_VB5.0.20_nslookup.txt <-- NSLookup working
Xubuntu1604_VB5.0.20_VBox.log <-- The VBox log from that VM's execution
Xubuntu1604_VB5.0.24_nslookup.txt <-- NSLookup failing
Xubuntu1604_VB5.0.24_VBox.log <-- The VBox log from that VM's execution

Also could you kindly correct the spelling of "reslove" to "resolve" in the description. I am unable to find documented how to update the description field.

[Valery Ushakov]

Is that resolv.conf from the guest or from the host? I need the one from the host. Sorry, I was not clear about that.

[mlueck]

It will be the same for both. Ubuntu client's always have that DNS caching server running on 127.0.0.1, then that reaches out to the real DNS server on the LAN as needed.

[Valery Ushakov]

Can you try a test build r108546+, please.

[mlueck]

Sure. Which build is correct for Xubuntu 14.04 x64? Is there a .deb package of the proposed build I am to evaluate?

[Valery Ushakov]

Generic "Linux 64-bit" *.run. We don't build all possible OS/versions permutations for test builds.

[Frank Mehnert]

If the .run installer is not enough, here is a package which should install on your Xubuntu 14.04. :-)

[mlueck]

Samle files from execution with requested build VirtualBox-5.0.25-108568-Linux_amd64.run

[mlueck]

I pulled down and used files:
VirtualBox-5.0.25-108568-Linux_amd64.run
Oracle_VM_VirtualBox_Extension_Pack-5.0.25-108568.vbox-extpack

Please find just attached 15575_Req2.zip containing:

WinXP_VB5.0.25_nslookup.txt <-- NSLookup working
WinXP_VB5.0.25_VBox.log <-- The VBox log from that VM's execution
Xubuntu1604_VB5.0.25_nslookup.txt <-- NSLookup working
Xubuntu1604_VB5.0.25_VBox.log <-- The VBox log from that VM's execution

Looks healed to me. Thank you so much. I look forward to the next official release.

[mlueck]

This issue was resolved with the official new build:
virtualbox-5.1_5.1.0-108711~Ubuntu~trusty_amd64.deb

Thank you very much!

[Frank Mehnert]

Thanks for the feedback! The same fix should be part of VBox 5.0.26.